Skip to content

R0020/2026-03-25/Q003 — Query Definition
Research R0020 — Prompt Engineering Gaps
Run 2026-03-25
Query Q003

Query as Received

Do mainstream prompt engineering guides and best-practice documents discuss the importance of explicit imperative constraints (MUST DO / MUST NOT DO directives) in prompts?

Query as Clarified

  • Subject: Mainstream prompt engineering guidance from major AI vendors and widely-cited industry sources
  • Scope: Whether these documents discuss and recommend the use of imperative, enforceable language (MUST, MUST NOT, NEVER, ALWAYS) as a technique for controlling AI behavior, as distinct from general clarity advice
  • Evidence basis: Official vendor documentation (OpenAI, Anthropic), industry guides, practitioner publications

Ambiguities Identified

  1. "Imperative constraints" could range from general clarity advice ("be specific") to RFC 2119-style enforcement language (MUST/SHALL/MUST NOT). The query asks about the stronger form.
  2. The distinction between "be clear and explicit" (general advice) and "use MUST/MUST NOT directives" (specific technique) is important — the former is ubiquitous, the latter is more specific.
  3. "Importance" is subjective — does the guide merely mention constraints, or does it position them as a core technique?

Sub-Questions

  1. Do major vendor prompt engineering guides explicitly recommend imperative language (MUST, MUST NOT, NEVER, ALWAYS)?
  2. How do guides frame the relationship between constraint language and output reliability?
  3. Is there a distinction in the guides between general clarity and specific enforcement directives?
  4. Do guides discuss the trade-offs or limitations of imperative constraints?

Hypotheses

ID Hypothesis Description
H1 Yes, imperative constraints are a documented best practice Mainstream guides explicitly recommend MUST/MUST NOT directives as a core technique for controlling AI behavior
H2 No, imperative constraints are not discussed Mainstream guides focus on general clarity and examples rather than imperative enforcement language
H3 Partially — implicit but not explicit emphasis Guides recommend clarity and specificity in ways that encompass constraint language, but do not specifically call out imperative directives as a distinct technique