Purpose
Guide splitting large epics into right-sized user stories using proven patterns. Recommends the best splitting strategy based on the epic's characteristics — workflow steps, business rules, data variations, user personas, or platform differences.
Key Concepts
9 Splitting Patterns (Richard Lawrence)
| # |
Pattern |
When to Use |
Example |
| 1 |
Workflow Steps |
Epic follows a multi-step process |
"Checkout" → Cart, Payment, Confirmation |
| 2 |
Business Rules |
Different rules for different cases |
"Apply discount" → By tier, volume, promo |
| 3 |
Happy/Unhappy Path |
Error handling adds complexity |
"Login" → Success, Wrong password, Locked |
| 4 |
Input Variations |
Multiple data types or sources |
"Import data" → CSV, API, manual entry |
| 5 |
Data Types |
Different entities need same operation |
"Notifications" → Email, SMS, push |
| 6 |
Operations (CRUD) |
Create, Read, Update, Delete |
"Manage users" → Create, view, edit, disable |
| 7 |
Role/Persona |
Different users need different versions |
"Dashboard" → PM view, Exec view, Dev view |
| 8 |
Platform |
Needs to work across contexts |
"Search" → Web, mobile, API |
| 9 |
Performance |
Functional first, optimize later |
"Report" → Generate (slow), then optimize |
Application
Question 1: Describe the Epic
Agent asks: "What's the epic? Share the title and a 2-3 sentence description."
Question 2: Epic Characteristics
Agent asks: "What makes this epic big? (Select all that apply)"
- Multiple workflow steps
- Complex business rules
- Multiple user types
- Multiple platforms/channels
- Error handling / edge cases
- Performance requirements
- Multiple data types
Question 3: Apply Patterns
Agent recommends 2-3 splitting patterns and generates stories:
## Recommended Split: [Pattern Name]
### Original Epic
[Epic description]
### Split Stories
1. **[Story 1]:** As a [persona], I want to [first slice], so that [value]
2. **[Story 2]:** As a [persona], I want to [second slice], so that [value]
3. **[Story 3]:** As a [persona], I want to [third slice], so that [value]
...
### Validation
- [ ] Each story delivers independent value
- [ ] Stories are small enough for 1 sprint
- [ ] Combined stories cover the original epic
- [ ] Stories are testable independently
Quality Rubric
| Dimension |
0 |
1 |
2 |
| Pattern Fit |
Random split |
Pattern applied but forced |
Pattern matches epic nature |
| Story Independence |
Stories depend on each other |
Some independence |
Each story deployable alone |
| Coverage |
Stories miss parts of epic |
Most covered |
Full epic coverage + validation |
| Size |
Still too big (multi-sprint) |
Mostly right-sized |
All stories fit in 1 sprint |
References
Related Skills
skills/specification/user-story/SKILL.md — Write the resulting storiesskills/specification/user-story-splitting/SKILL.md — Splitting patterns referenceskills/planning/epic-hypothesis/SKILL.md — Epic that needs splitting
External Frameworks
- Richard Lawrence, Patterns for Splitting User Stories (AgileForAll)
Skill type: Interactive
Domain: Planning & Prioritization
1---2name: epic-breakdown-advisor3description: Guide splitting large epics into right-sized user stories using Richard Lawrence's 9 proven splitting patterns. Recommends the best pattern based on epic characteristics.4---56## Purpose78Guide splitting large epics into **right-sized user stories** using proven patterns. Recommends the best splitting strategy based on the epic's characteristics — workflow steps, business rules, data variations, user personas, or platform differences.910---1112## Key Concepts1314### 9 Splitting Patterns (Richard Lawrence)1516| # | Pattern | When to Use | Example |17|---|---------|------------|---------|18| 1 | **Workflow Steps** | Epic follows a multi-step process | "Checkout" → Cart, Payment, Confirmation |19| 2 | **Business Rules** | Different rules for different cases | "Apply discount" → By tier, volume, promo |20| 3 | **Happy/Unhappy Path** | Error handling adds complexity | "Login" → Success, Wrong password, Locked |21| 4 | **Input Variations** | Multiple data types or sources | "Import data" → CSV, API, manual entry |22| 5 | **Data Types** | Different entities need same operation | "Notifications" → Email, SMS, push |23| 6 | **Operations (CRUD)** | Create, Read, Update, Delete | "Manage users" → Create, view, edit, disable |24| 7 | **Role/Persona** | Different users need different versions | "Dashboard" → PM view, Exec view, Dev view |25| 8 | **Platform** | Needs to work across contexts | "Search" → Web, mobile, API |26| 9 | **Performance** | Functional first, optimize later | "Report" → Generate (slow), then optimize |2728---2930## Application3132### Question 1: Describe the Epic3334**Agent asks:** "What's the epic? Share the title and a 2-3 sentence description."3536### Question 2: Epic Characteristics3738**Agent asks:** "What makes this epic big? (Select all that apply)"39401. Multiple workflow steps412. Complex business rules423. Multiple user types434. Multiple platforms/channels445. Error handling / edge cases456. Performance requirements467. Multiple data types4748### Question 3: Apply Patterns4950Agent recommends 2-3 splitting patterns and generates stories:5152```markdown53## Recommended Split: [Pattern Name]5455### Original Epic56[Epic description]5758### Split Stories591. **[Story 1]:** As a [persona], I want to [first slice], so that [value]602. **[Story 2]:** As a [persona], I want to [second slice], so that [value]613. **[Story 3]:** As a [persona], I want to [third slice], so that [value]62...6364### Validation65- [ ] Each story delivers independent value66- [ ] Stories are small enough for 1 sprint67- [ ] Combined stories cover the original epic68- [ ] Stories are testable independently69```7071---7273## Quality Rubric7475| Dimension | 0 | 1 | 2 |76|-----------|---|---|---|77| **Pattern Fit** | Random split | Pattern applied but forced | Pattern matches epic nature |78| **Story Independence** | Stories depend on each other | Some independence | Each story deployable alone |79| **Coverage** | Stories miss parts of epic | Most covered | Full epic coverage + validation |80| **Size** | Still too big (multi-sprint) | Mostly right-sized | All stories fit in 1 sprint |8182---8384## References8586### Related Skills87- `skills/specification/user-story/SKILL.md` — Write the resulting stories88- `skills/specification/user-story-splitting/SKILL.md` — Splitting patterns reference89- `skills/planning/epic-hypothesis/SKILL.md` — Epic that needs splitting9091### External Frameworks92- Richard Lawrence, *Patterns for Splitting User Stories* (AgileForAll)9394---9596**Skill type:** Interactive97**Domain:** Planning & Prioritization
nandanosql