User Story Generator

StrategyBeginner

Given feature requirements, generates complete backlog items including persona-based user stories, acceptance criteria, and development tasks.

Trigger/story

Frequency1-2x/week

PM preparing backlog before sprint planning? Run /story to auto-extract user stories from the PRD

Scrum master? Validate and improve quality of team-written user stories

User StoriesAgileBacklogScrum

How It Works

Run /story [feature description]

↓

Phase 1: 3 generation tasks in parallel

persona-map

Classify by persona

ac-write

Write acceptance criteria

task-break

Break down dev tasks

↓

Set priorities + estimate story points

↓

✓ User stories + AC + task list

Skill Code

# User Story Generator Skill
## Trigger: /story [feature or requirement]

When invoked:

1. Identify user personas affected
2. Generate stories in standard format

3. Output format:
---
## 📝 User Stories: [Feature]

### Story 1 (P0 — [X] points)
**As a** [persona]
**I want to** [action]
**So that** [benefit]

**Acceptance Criteria:**
- [ ] Given [context], when [action], then [result]
- [ ] Given [context], when [action], then [result]
- [ ] Edge case: [scenario] → [expected behavior]

**Dev Tasks:**
- [ ] [Backend: task]
- [ ] [Frontend: task]
- [ ] [Test: task]

### Story 2 (P1 — [X] points)
[repeat format]

### Summary
| Priority | Stories | Total Points |
|----------|---------|-------------|
| P0 | [N] | [X] |
| P1 | [N] | [X] |
| P2 | [N] | [X] |
---

Copy and paste into your CLAUDE.md to start using immediately.

How User Story Generator Works

User Story Generator takes high-level requirements, breaks them into user stories following the 'As a [role], I want [goal], so that [benefit]' format, and attaches detailed acceptance criteria with test scenarios for each story.

When to Use User Story Generator

Accelerates sprint planning by transforming vague requirements into well-structured, estimable user stories — ensures acceptance criteria are thorough enough that developers and QA have a shared understanding of 'done'.

Key Strengths

Follows standard user story format consistently
Generates detailed acceptance criteria with test scenarios
Breaks large requirements into right-sized stories
Creates a shared definition of done for dev and QA

Same Category

Strategy View All

PRD Writer

Generates comprehensive PRDs through structured Socratic questioning.

Competitor Analysis

Systematically analyzes competitors and generates comparison matrices.

OKR Planning Guide

Guides team/individual OKR creation through a structured process.

Popular in Other Categories

Session Summary

WorkflowAutomatically summarizes changes and next steps at the end of a work session.

Smart Commit

CodingAnalyzes changes and auto-generates meaningful commit messages.

CLAUDE.md Builder

ProductivityAnalyzes your project and auto-generates an optimized CLAUDE.md.