| name | write-feature-spec |
| description | Create or refresh an execution-oriented feature brief in specs/. Use this when asked to write a feature specification, implementation brief, or task-ready plan for agents. |
Use this workflow when turning a request into a reusable repository spec:
- Read
specs/README.md.
- Read
specs/TEMPLATE.md.
- Read
docs/technical-notes/README.md and the notes relevant to the feature area.
Authoring rules:
- Create or update the spec in
specs/feature-briefs/.
- Keep the spec task-oriented: context, goal, touchpoints, constraints, acceptance criteria, and validation.
- Explicitly list the technical notes that must be read before implementation.
- Do not restate durable architecture rules in full. Link back to
docs/technical-notes/ instead.
- If an older brief already exists for the same feature, update it or clearly supersede it instead of creating ambiguous duplicates.
A good spec should help an agent execute work with less guesswork while still relying on the technical notes for stable repository conventions.