All setups
ProductSetupAI-generated
User Story Generator
Break down a feature or epic into well-scoped stories with testable acceptance criteria
What it is
Break down a feature or epic into well-scoped stories with testable acceptance criteria
Decomposes a feature description or epic into individually shippable user stories, each with a role-based story statement and a numbered list of binary acceptance criteria. Includes a size estimate with rationale so sprint planning starts with clarity.
What you'll get
Custom instructionsCompiled from your answers, editable before you export.
User story format guideA compact reference for the story format, acceptance-criteria rules, and size definitions so every story the team writes follows the same structure.
Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.
Try it on
Break down a notifications center epicscenario · built in
Claude should produce at least three distinct stories — one per notification type or user intent (task updates, @mentions, deadline reminders). Each story must follow the "As a [role], I want [feature] so that [benefit]" format, include a numbered list of binary acceptance criteria, and carry a size estimate with rationale. Stories must not be bundled into one giant story. Claude should not invent notification frequency data or engagement statistics.
Generate stories for a password reset flowscenario · built in
Claude should produce stories covering: requesting a reset (happy path), the email link expiry behavior, and resetting the password successfully. The acceptance criteria must address the 15-minute expiry as a specific testable state (e.g., "when a user clicks an expired link, the system shows an error and offers to resend"). Size estimates must be realistic. Claude must not fabricate support ticket volume or churn statistics.
Compiled preview
You write user stories for {{productName}}.
Feature or epic to break down: {{epicOrFeature}}
Primary user role for these stories: {{primaryUserRole}}
{{#if edgeCaseContext}}
Edge cases or constraints to account for: {{edgeCaseContext}}
{{/if}}
For each user story, write:
- Story title (5–8 words)
- Story statement: "As a [role], I want [feature] so that [benefit]."
- Acceptance criteria (numbered list; each criterion is binary — pass or fail, not subjective)
- Size estimate (XS / S / M / L / XL) with a one-sentence rationale
Rules:
1. Each acceptance criterion must be testable: "the system displays a confirmation message" passes; "users feel confident" does not.
2. Write separate storie
…