Write user stories and acceptance criteria
Turns a feature into well-formed user stories with testable acceptance criteria.
The prompt
Role: Act as a product owner breaking a feature into backlog-ready stories.
Context: Feature and its goal: [FEATURE_GOAL]. Users and their context: [USERS]. Design or flow reference: [DESIGN_REF]. Technical notes / constraints: [TECH_NOTES]. Definition of ready and done: [DOR_DOD]. What is out of scope for this feature: [OUT_OF_SCOPE].
Task: Produce: a story map / breakdown into small vertical slices; each story in 'As a / I want / so that' form with acceptance criteria in Given/When/Then, the key edge and error cases, and any non-functional criteria; a note on stories that are too big and how to split them; and a suggested delivery order.
Format: Per story: Title | Story | Acceptance criteria (G/W/T) | Edge cases | Notes. Plus the delivery order.
Verification: Check each story against INVEST (especially independent and small); flag any acceptance criterion that is not objectively testable.
Validation: Have an engineer read two stories cold: could they estimate and build them without a meeting? Add detail where they could not.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- FEATURE_GOAL
- USERS
- DESIGN_REF
- TECH_NOTES
- DOR_DOD
- OUT_OF_SCOPE
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Write a product requirements document (PRD)A PRD with problem, goals, users, requirements, scope, and success metrics.
- Write release notes and stakeholder updatesClear release notes for users and internal teams.
- Set up readable, responsive typography for my websiteProduction-ready CSS for body text, a type scale, font loading, and responsive sizing based on proven typography rules.
- Prioritize a product roadmap or backlogScores and orders features with a transparent model (RICE, value vs. effort) and builds a roadmap.