User stories with acceptance criteria
OfficialOfficial · updated Nov 4, 2026 · v1.0.1
Turns a feature into user stories with Given/When/Then acceptance criteria, edge cases, out-of-scope notes, and an INVEST check per story.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- A PRD or feature is agreed and needs to go into the backlog as tickets
- A ticket exists but nobody can say when it's done
What you give it
- Feature description or PRD section
- User roles involved
- Known rules and limits (optional)
What you get
A set of user stories, each with Given/When/Then scenarios, edge cases, out-of-scope notes, an INVEST line, and open questions.
Changelog
- v1.0.1 · Nov 4, 2026 · Example: Story 3 now has a failure scenario, a removed user who tries to sign in again is refused.
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- INVEST in Good Stories, and SMART Tasks (XP123) (2026-11-04)
- Given When Then (Martin Fowler) (2026-11-04)
- Introducing BDD (Dan North) (2026-11-04)
- Essential XP: Card, Conversation, Confirmation (Ron Jeffries) (2026-11-04)
Related skills
- PRD from messy notes Turns notes, Slack threads, and call notes into a PRD: problem with evidence, goals and non-goals, metrics, must/should/could requirements, and flagged gaps.
- Spec review before build Reviews a PRD or spec before build for ambiguity, missing empty/loading/error/permission states, metrics, rollout, and a first-time user walk-through.
- Feature prioritization with RICE Scores a backlog with RICE or ICE, shows the math per item, tests sensitivity, recommends a cut line for capacity, and flags dependencies.
- Bug report from a support ticket Turns a customer complaint into an engineering-ready bug report: steps to reproduce, expected vs actual, environment, impact, evidence, and questions to ask.