epic-breakdown-advisor

Break large epics into vertically sliced user stories with acceptance criteria.

1|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/yuyuxinli/moodcoco --skill epic-breakdown-advisor-yuyuxinli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-breakdown-advisor
Source: https://github.com/yuyuxinli/moodcoco/tree/main/.claude/skills/epic-breakdown-advisor
Command: npx skills add https://github.com/yuyuxinli/moodcoco --skill epic-breakdown-advisor-yuyuxinli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large backlog epics are often too big, vague, or technically horizontal to estimate, sequence, or deliver safely; this Skill provides a methodical process to turn those epics into vertically sliced, sprint-sized user stories that deliver observable user value.

Core Features & Use Cases

  • Pre-split INVEST validation: Walks through Independent, Negotiable, Valuable, Estimable, and Testable checks (except Small) and stops or reframes work that lacks user value.
  • Nine sequential splitting patterns: Applies Humanizing Work patterns (workflow steps, CRUD, business rules, data variations, UI entry, major-effort, simple/complex, defer performance, spike) to find the right vertical slice.
  • Split evaluation & templates: Produces story titles, As a/I want/so that summaries, acceptance criteria, rationale, and guidance for further splitting or deprioritization.
  • Use case: Product managers preparing a large onboarding or reporting epic for sprint planning can paste the epic and get a validated, pattern-driven breakdown into sprint-sized stories.

Quick Start

Provide the epic title, description or hypothesis, acceptance criteria, target persona, and a rough estimate and ask the agent to break the epic into vertical user stories using the Humanizing Work nine-pattern sequence.

Frequently Asked Questions about epic-breakdown-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down large epics into sprint-ready user stories?

To break down large epics into sprint-ready user stories, apply nine sequential splitting patterns to create vertically sliced stories that preserve observable user value. This process transforms vague, technically horizontal backlog items into estimable chunks for sprint planning.

What are the Humanizing Work nine sequential splitting patterns for story splitting?

The Humanizing Work story splitting patterns are workflow steps, CRUD, business rules, data variations, UI entry, major-effort, simple/complex, defer performance, and spike. Applying these patterns sequentially helps product managers find the right vertical slice to deliver observable user value safely.

How do I validate an epic before splitting it into smaller user stories?

To validate an epic before splitting, run pre-split INVEST checks for Independent, Negotiable, Valuable, Estimable, and Testable attributes. This validation stops or reframes work that lacks user value before applying story splitting patterns to generate sprint-sized templates.

What inputs do I need to provide for epic backlog refinement and story generation?

For epic backlog refinement and story generation, provide the epic title, description or hypothesis, acceptance criteria, target persona, and rough estimate. These inputs enable INVEST validation and the application of sequential splitting patterns to generate sprint-sized story templates.

Can I use vertical slicing for backlog items that are too technically horizontal to estimate?

Yes, vertical slicing is specifically designed for backlog items that are too technically horizontal to estimate or deliver safely. By applying sequential splitting patterns, you can restructure horizontal work into vertically sliced user stories that maintain observable user value.

What is included in the generated user story templates after splitting an epic?

Generated user story templates include story titles, As a/I want/so that summaries, acceptance criteria, rationale, and guidance for further splitting or deprioritization. These templates provide sprint-ready outputs for backlog estimation, sequencing, and refinement.