User Story
Write user stories for agile sprint planning, product backlogs, and stakeholder communication with acceptance criteria, story points, and dependencies.
Overview
Generate complete user stories in under 60 seconds with acceptance criteria, story points estimation, and dependencies for agile sprint planning and product backlogs.
Use Cases
- Break down feature specs into sprint-ready user stories during backlog refinement sessions
- Generate user stories for new SaaS features before sprint planning meetings
- Create acceptance criteria for mobile app features in standard agile format
- Write user stories for API endpoints during technical planning sprints
- Document product requirements as user stories for stakeholder review
Template
Create user stories for:
Feature/Epic: {{feature}}
User persona: {{persona}}
Context:
{{context}}
Format: {{format}}
Include:
- User story statement (As a... I want... So that...)
- Acceptance criteria
- Definition of done
- Story points estimation
- Dependencies
- Notes and assumptions
Number of stories: {{numberOfStories}}
Properties
- feature: Single-line Text
- persona: Single Selection (default:
End user)- Options: End user, Admin, Power user, New user, Business user, and 1 more
- context: Multi-line Text
- format: Single Selection (default:
Standard)- Options: Standard (As a… I want…), Job story (When… I want… So I can…), Feature-driven
- numberOfStories: Single Selection (default:
3)- Options: 1 story, 3 stories, 5 stories, 10 stories
Benefits
- Save 20+ minutes per story - Generate complete user stories with acceptance criteria instead of writing from scratch
- Consistent story format across sprints - Every story includes standardized acceptance criteria, definition of done, and story points
- Identify dependencies early - Automatically highlights technical dependencies and integration points before sprint planning
- Better story point accuracy - AI considers complexity, dependencies, and edge cases when estimating effort
- Reduce refinement meeting time - Come to backlog refinement with draft stories already written
Example Output
Here’s what this template generates for a two-factor authentication feature:
User Story: As a mobile banking app user I want to receive an SMS verification code when making transactions over $1,000 So that my account is protected from unauthorized large transactions
Acceptance Criteria:
- Transaction amount validation triggers at exactly $1,000.01
- SMS code sent within 30 seconds of transaction initiation
- Code is 6 digits, numeric only
- Code expires after 10 minutes
- Transaction blocked until valid code entered
- Maximum 3 verification attempts before transaction cancellation
- Transactions under $1,000 proceed without SMS verification
- Clear error messages for invalid/expired codes
Definition of Done:
- Code merged and deployed to production
- Unit and integration tests passing (>90% coverage)
- QA validated on iOS and Android
- Performance testing shows <2s SMS delivery
- Security audit completed
- User documentation updated
- Analytics tracking implemented
Story Points: 8
Dependencies:
- SMS gateway provider integration
- Phone number verification system
- Transaction processing service must support verification workflow
Notes:
- Consider rate limiting to prevent SMS abuse
- Need fallback method if SMS delivery fails
- Verify compliance with financial regulations for 2FA
- International SMS delivery may have delays
Common Mistakes to Avoid
Vague acceptance criteria User stories need specific, testable conditions. “User can log in successfully” is too broad. Better: “User enters valid credentials and sees dashboard within 2 seconds.”
Missing edge cases AI helps you think through scenarios you might miss: What happens when the SMS doesn’t arrive? What if the user changes their phone number mid-transaction? Good user stories address these upfront.
Skipping the ‘So that’ clause The value statement matters. “As a user I want two-factor authentication” doesn’t explain why. “So that my account is protected from unauthorized access” gives the team context for design decisions.
Overly large stories If a story estimates at 13+ points, it’s probably an epic. Break it into smaller stories that fit in a single sprint.
Ignoring non-functional requirements Performance, security, and accessibility belong in acceptance criteria. “SMS code delivered within 30 seconds” is just as important as “SMS code is 6 digits.”
Frequently Used With
- Feature Spec - Write detailed technical specifications before breaking into user stories
- Release Notes - Document completed user stories for product changelog
- PRD Template - Create product requirements documents that feed into user story creation
Get Started with Migi
Want to access this template and 80+ others instantly from anywhere on your Mac?