Writing Guardrails
Follow these rules for governed prose.
Scope
- Govern: prose in
plan.md,spec.md,mission.md,architecture.md(project and plan level), decision logs, ADR fragments inspecs/_decision/,review-findings.md, verification reports, implementation summaries, GitHub PRs, issues, and comments. - Leave unchanged: Gherkin, Background bullets, tables, ASCII diagrams, delta markers, and validator-owned RFC keyword casing.
Rules
- Lead with the conclusion. State the decision, result, or finding first. Give reasons afterward.
- Express one idea per sentence. Split sentences that make separate claims.
- Name the actor. State who or what performs each action.
- Name each thing once and reuse that name. Do not switch to a synonym for the same thing later in the text.
- Assume the reader does not know the method, concept, technology, or system. Explain unfamiliar concepts in simple language before using specialized terms.
- Remove filler, hedges, superlatives, intensifiers, hyperbole, and promotional language. Use measurable evidence when making claims about scale or quality.
- Use neutral, matter-of-fact language. Avoid colloquial, metaphorical, dramatic, and rhetorical language.
- State the current result. Do not narrate attempts, revisions, or reasoning history unless that history is relevant.
- Do not use em dashes. Use a period, comma, or colon.


