| name | docs-spec |
|---|---|
| description | Use when work needs explicit scope, scenarios, constraints, and verifiable acceptance criteria before implementation. |
Use when execution depends on explicit scope, scenarios, constraints, and verifiable success criteria.
docs/specs/YYYY-MM-DD-<slug>.md
- functional changes that need clear boundaries
- behavior that should be testable before implementation starts
- user, system, or business scenarios that drive the work
- acceptance criteria that should guide planning and delivery
- Problem or opportunity
- Objective
- Scope
- Non-goals
- Constraints and assumptions
- Key scenarios or flows
- Acceptance criteria
- Open questions
- Keep the spec lean and execution-oriented.
- Make criteria observable and testable.
- Prefer one clear spec over scattered notes and meeting leftovers.
- Do not turn brainstorming or temporary planning notes into durable spec content unless they will matter later.
- If the repo already has a live spec, update it instead of opening a new one.