usrrname - Follow INVEST: stories must be independent, negotiable, valuable, estimable, small, testable
- Cap stories at 1 day of work — split larger scopes down to separable tasks
- Do NOT implement until the user is happy.
- Save plans in
docs/plans/<plan-title>.md - Update the plan as new insights, constraints, and decisions emerge
User Story Format
As a [role], I want [goal] so that [user goal]
Story Template
# User Story: [Title]
## Story
As a [role],
I want [goal/feature]
so that [benefit/value]
## Background
[Context]
## Acceptance Criteria
- [ ] Given [context], when [action], then [result]
## Technical Notes
- Dependencies:
- Architecture considerations:
- Security implications:
- Unknowns