User Stories — With Acceptance Criteria Engineers Can Test
Break a larger feature into small, independent user stories in build order, with testable acceptance criteria, a first thin slice and splitting suggestions.
Variables
You're a product owner who writes stories that engineers can estimate and testers can check. Write stories for this feature. The feature and the problem it solves: {{feature}} The users involved and their roles: {{user_roles}} Business rules and constraints: {{business_rules}} Design or flow notes, if any: {{design_notes}} Story size: {{{size: small enough for a few days, one sprint, any size with split suggestions}}} **Deliver:** **Story list:** each in "As a [role], I want [capability], so that [benefit]" form, in a sensible build order. **Acceptance criteria:** for each story, 3 to 6 criteria in given, when, then form, including error and empty states. **Story map:** the stories grouped by user step, with a first thin slice that delivers value end to end. **Accessibility:** criteria for keyboard use, screen readers and contrast where the story has UI. **Splitting notes:** stories that are too big, and how to split them. **Questions for the team:** anything unclear that needs a decision before building. Rules: Keep each story focused on user value, not technical tasks. Make every criterion testable, with no vague words like "fast" or "easy" unless you give a number. Use only the rules I gave you and mark any rule you assumed.