Match the docs to the template: verification chain, /sdd-clarify, plan review
The wiki mirrored the defects the repository just fixed, and in three places it
quoted them verbatim - the Given/When/Then acceptance-criterion format, the
traceability header without a Test column, and a "progress.md you add yourself"
that the template never declared.
Specs and Plans
- Five acceptance-criterion shapes replace Given/When/Then alone, with the reason:
a scenario notation mangles always-true, state and optional-feature requirements
- shall/should discipline and the rejection list
- Verified: field in the step schema, Test column and open|built|verified in the
traceability table, and the chain restated as spec -> plan -> code -> test
- Out-of-scope reasons and the four-column assumption register
- done/ requires evidence; Deprecated supersedes an invalidated spec
Memory Bank
- progress.md and the imported five-phase vocabulary are gone
- Last updated must be refreshed, and /sdd-compile checks it against the git log
- Says who reads these files, which nothing did before
- One gate for the architecture snapshot write, and specs/plans no longer trigger drift
Commands
- New /sdd-clarify section: four lists, list-don't-resolve, one closing question,
and why a cold second context finds what the interview could not
- /sdd-compile: verdict vocabulary, the narrow definition of evidence, re-derivation
- /sdd-plan: hand-off for review, contradicting survey returns to Mode C
- /sdd-specify: brownfield reads code before asking, split offer at the budget ceiling
- /sdd-setup: reads the repo before asking what the repo answers
- The fast path documented as part of the method
Hands-On Walkthrough
- New 2.3 clarify exercise with the question worth asking the room
- Plan review promoted to a five-minute exercise both roles do
- Verified: made visible during implementation, evidence made visible at acceptance
- Two rows in the flow table are humans reading, not tools producing
Also: eight commands to nine throughout, .specs/ documented as shipping empty with
docs/history/ explained, Home is honest that this is variance reduction and not speed,
and Design Decisions gains "one action, one autonomy level".
Add the FeatherSpec wiki
Fifteen pages carrying the reference material the README no longer holds:
getting started for both tools, all eight commands in detail, the spec and
plan documents, the Memory Bank, the repository layout, configuration,
extension, the interop matrix with its sources, the design decisions behind
commands-not-skills and the single-source rule, ejection to one tool,
migration from the predecessor template, troubleshooting, and an FAQ.
Plus the workshop as a Hands-On Walkthrough: one complete SDD cycle on a tip
splitter, PO and Dev alternating at the same keyboard.