PM-201a · Module 2

Hard Lines vs. Soft Guidelines

3 min read

Not all constraints carry the same weight. Some are hard lines — absolute requirements that the output must meet regardless of other considerations. Others are soft guidelines — preferences that should be followed when possible but may yield to higher-priority constraints. Writing these at the same level of emphasis is a mistake. When constraints conflict and no priority is specified, the model resolves the conflict on its own — and usually not the way you intended.

[HARD LINES — must / must not]
- Must: include a section for each of the three risk categories
- Must: stay within 300 words
- Must not: include pricing figures of any kind
- Must not: recommend specific vendors or products

[SOFT GUIDELINES — prefer / avoid]
- Prefer active voice over passive
- Prefer specific evidence over general statements
- Avoid jargon where plain language serves equally well
- Avoid more than three bullet points per section

[CONFLICT RESOLUTION — when constraints compete]
"If length and completeness conflict, prioritize completeness on the three required risk categories, then cut from optional sections."

Do This

  • Use must/must-not for non-negotiable constraints
  • Use prefer/avoid for guidelines that can yield to higher priorities
  • Write an explicit conflict resolution rule when two hard lines may compete
  • Separate hard lines from soft guidelines visually in the prompt

Avoid This

  • Do not write all constraints at the same emphasis level
  • Do not assume the model will infer which constraint takes priority
  • Do not use soft language for hard requirements: "please try to stay under 200 words"
  • Do not write contradictory hard lines — resolve the contradiction before prompting