Three defects the first sweep left behind, each caught by a rule the guard did not yet have. Statuses. RULES.md gives three; the tree had 25 values, and the free-text ones were carrying progress. "Implemented (wiring landed)" and "Ratified (rev. 2e). Rev. 2e adds the OpenTaskByPR lookup. Rev. 2d revised section 10..." were both changelogs living in the one field the other rules exempt. Every PRD now declares Draft, Approved or Finalised and nothing else; five that declared nothing now declare one. A revision number moves to **Revision:**, a pointer to the authoritative document to **Authority:**, and what a past revision changed to git. CLAUDE.md's citation of state-store-contract rev. 2e still resolves. Stale cross-references. "Supersedes the 2026-09-03 open question", "this bullet previously said", "an earlier draft of this document claimed" all point at text the reader cannot see, because it was replaced. A supersede marker survives only when it names a file, a section or a symbol that can be found. Temporal hedges. 100 uses of today, currently and right now across 31 files. Each dates its sentence to the day it was written: "[notify] today is one webhook URL, read in one place" stops being true the moment this design lands, while still reading as the premise it rests on. The header-field exemption was also too wide. "**Date:** 2026-09-03, Channel resolved 2026-09-22" smuggled a dated status into the one line the rules did not read; the exemption is now a Date holding only a date and a Status holding only one of the three.
43 lines
2.5 KiB
Markdown
43 lines
2.5 KiB
Markdown
# PRD writing rules
|
|
|
|
These rules apply to every file in `docs/prds/`.
|
|
|
|
- Search existing PRDs, issues, architecture records, and code first. Do not ask
|
|
the maintainer to repeat recorded requirements.
|
|
- A newer maintainer decision overrides an older design. Mark the old design as
|
|
superseded instead of preserving or defending it.
|
|
- Write plain English. Use a technical term only when the reader needs that
|
|
exact contract or concept.
|
|
- Use the shortest direct sentence. Write “When upgraded, existing instances
|
|
are migrated to the database,” not a description of an importer seeding
|
|
absent resources.
|
|
- State each fact once. Do not repeat a heading, summarize a list before showing
|
|
it, or restate a decision afterward.
|
|
- Every sentence must add a decision, requirement, constraint, evidence, or
|
|
verification step. Delete narration and explanations of obvious text.
|
|
- Do not turn a requested outcome into extra product features. Keep inferences
|
|
open until the maintainer or repository evidence settles them.
|
|
- Do not create a process for a logical boundary. Add one only when it must
|
|
deploy, scale, start, secure, or fail separately.
|
|
- Describe working behavior, not explanatory UI around missing behavior. State
|
|
what users can do and how success is proved.
|
|
- Before approval, use independent read-only reviewers to check a cross-cutting
|
|
PRD for missing behavior and exaggerated claims. Verify and synthesize their
|
|
findings; do not copy their prose.
|
|
- Before requesting approval, review every sentence for complexity, repetition,
|
|
and unsupported scope.
|
|
- Write nothing whose truth expires. No `file.go:123` citations (cite the file
|
|
and the symbol), no progress reports on the work being designed, no dated
|
|
status claims, and no record of how a finding was produced. A phased plan is
|
|
durable design; which phase is finished is not. Do not refer to what this
|
|
document used to say: the reader cannot see it. A supersede marker is fine
|
|
when it names a file, a section or a symbol they can find. `task docs:prds`
|
|
enforces this.
|
|
- Every PRD carries one of three statuses, and nothing else in that field.
|
|
`Draft` until the maintainer explicitly approves it, `Approved` once they
|
|
have and while the work is being built, `Finalised` when the work is
|
|
complete. A finalised PRD does not change; supersede it with a new one
|
|
instead. A revision number belongs in `**Revision:**`, a pointer to the
|
|
authoritative document in `**Authority:**`, and what a past revision changed
|
|
belongs in git.
|