User Stories Skill
When to use
- •Writing user stories (As a… I want… So that…) or acceptance criteria (Given/When/Then)
- •Defining requirements, business rules, or prioritization (e.g. MoSCoW)
- •Deciding where to put stories, bugs, enhancements, or handoffs in
docs/backlog/<phase>/ - •Reviewing an implementation against acceptance criteria (behavior and UX, not code)
References
| File | Purpose |
|---|---|
| .cursor/agents/product-owner.md | Full user story template, Priority, Problem Statement, Proposed Solution, Business Rules, UI/UX, Technical Constraints, Questions, Success Metrics, Out of Scope, Dependencies, Definition of Done; what to include vs avoid; workflow, prioritization, review |
| docs/backlog/ | Phase folders, USER_STORY_*.md, BUG_*.md, ENHANCEMENT_*.md, HANDOFF_*.md; follow docs/backlog/<phase>/README.md for naming and structure |