Turn a Feature Idea into User Stories with Given/When/Then Criteria
Get a backlog-ready set of single-outcome user stories with testable Given/When/Then acceptance criteria, size estimates, and flags on stories too big for one sprint.
You getSummary table and for each story
Prompt
Act as a senior product manager who writes backlog-ready user stories for agile teams.
I will paste a feature idea right after this prompt. If it does not say who the users are, what problem it solves, or how long our sprints are, ask me up to 3 short numbered questions in one message and wait for my answers before writing anything.
Then break the feature into user stories.
Rules:
1. Use "As a..., I want..., so that..." with exactly one user type and one outcome. If an outcome contains "and", split the story.
2. Give each story 2-4 acceptance criteria in Given/When/Then form, each with a clear pass or fail result.
3. At least one criterion per story covers an error, empty state, or edge case.
4. Size each story S, M, L or XL. Mark any XL, or anything that would not fit one sprint, as "Too large" and suggest how to split it.
5. Order stories so the first one delivers a thin, usable slice on its own.
Output format:
- Summary table: ID | Story | Size | Sprint fit (Yes / Too large)
- For each story: ID and short title, the story, numbered Given/When/Then criteria, dependencies, split suggestion if flagged.
- Open questions: up to 5.
End with one line listing the assumptions you made and anything missing that could change scope.Example output
Tips and common edits
Why this works
- The one-user, one-outcome rule plus splitting on "and" stops vague stories that bundle several features together.
- Requiring an edge or error criterion per story catches empty states and failures QA would otherwise find late.
- Sizing with a Too large flag and split suggestion makes the output usable directly in sprint planning.
Use before backlog refinement or sprint planning. Paste your feature idea, rough notes or a Slack thread into ChatGPT, Claude or Gemini; know your users and sprint length so you can answer its questions.
Common edits
- Swap S/M/L/XL for story points on your team's Fibonacci scale.
- Ask for the stories as a CSV with columns ready to import into Jira or Linear.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write a Product Requirements Document from Your Raw Feature Notes
Turns pasted feature notes into a PRD where each requirement has numbered, testable acceptance criteria and missing details become open questions.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Draft an Internal Launch FAQ and Enablement Brief for Sales and Support
Turns your launch notes into a sales and support brief with talk tracks, a plain-answer FAQ, objection handling, and flags for claims that need legal or engineering sign-off.
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.
Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.