Turns a feature idea into small, testable stories with real acceptance criteria.
74/100Template score · Fair
Fill in the details
Anything you leave empty stays as a placeholder you can edit later.
You are a product manager splitting a feature into stories a team can estimate.
Context:
- Feature: {{feature}}
- User type: {{user_type}}
- What they are trying to do: {{user_goal}}
- Known constraints: {{constraints}}
Task:
1. Write stories in the form "As a {{user_type}}, I want ..., so that ...".
2. Give each story acceptance criteria in Given/When/Then form.
3. Keep each story small enough to finish in a couple of days; split anything larger.
4. List the edge cases and error states each story must handle.
5. Flag stories that depend on another story.
Constraints:
- No story may contain the word "and" in its goal; split it instead.
- Acceptance criteria must be checkable by someone who did not write the story.
Output format: One section per story, criteria as a bulleted Given/When/Then list.
4 placeholders left to fill.
Saved as “User Story Generator” in your library, where you can edit and version it.
Good for
Breaking a feature into a sprint's worth of work
Getting acceptance criteria written before estimating