Write User Stories with a Clear Template
Turn a rough idea into a clean user story with role, benefit and testable acceptance criteria, ready to drop into your backlog.
Last updated: July 2026 · Collective Brain
Good for
- Phrase backlog items quickly and consistently during sprint planning
- Turn a vague feature ticket into a testable story with acceptance criteria
- Give product owner and engineering a shared, precise language
The prompt
You are an experienced product owner writing user stories for an agile team.
Context:
- Product: [your product]
- User group: [role or persona]
- Goal or feature: [desired feature or user goal]
Task: Turn this input into a clear, actionable user story. Follow this output format exactly:
1. Title: short, descriptive heading (max. 8 words).
2. User story: use the pattern "As a [role], I want [capability], so that [benefit]." The benefit describes real value, not just a restatement of the capability.
3. Acceptance criteria: 3 to 5 criteria in Given/When/Then format, each independently testable and free of prescribed technical solutions.
4. Definition of ready: 3 short points that must be clarified before the team starts.
5. Open questions: 2 points you would clarify in my place before implementation.
Rules: Be concrete and avoid jargon. Do not invent numbers or deadlines; flag any gap as an open question instead. If my input is too thin, ask me up to three clarifying questions first, before writing the story.Replace the bracketed placeholders with your own details.
Frequently asked
How many user stories can I create at once?
The prompt is built for one clean story per run so the acceptance criteria and open questions are genuinely thought through. For a whole epic, feed features one after another or ask ChatGPT in a follow-up to split the story into smaller ones.
Does this prompt replace team alignment?
No. ChatGPT gives you a strong first draft, but it does not know your technical setup or your real priorities. Use the story as a basis for refinement and review the acceptance criteria together with engineering in particular.
Related
Rather have it done?
Prompts are a start.
Results are our job.
When the prompt should turn into real work that holds up consistently across every channel, we take over. Start free, finish professionally.