1.1 KiB
Feature Specification: {{FEATURE}}
Created: {{DATE}}
Original request: {{DESCRIPTION}}
Anything genuinely undecided gets an inline marker: the words NEEDS CLARIFICATION plus the open question, wrapped in square brackets. Keep at most 3 of them — pick a sensible default for everything else and record it under Assumptions.
User Stories
Describe who wants what and why. At least one story with priority P1; each story must be independently testable.
Story 1 — (P1)
As a …, I want …, so that ….
Acceptance: Given …, when …, then ….
Requirements
Numbered, verifiable statements of what the feature must do. Name the key entities (data the feature reads or writes) at the end.
- R1: The system must …
Entities: …
Success Criteria
Measurable, technology-agnostic outcomes that tell you the feature works (counts, durations, rates — things you can check without knowing the stack).
- S1: …
Assumptions
Defaults chosen for anything the request left open, plus explicit scope boundaries (what this feature deliberately does not cover).
- A1: …