epic-breakdown-advisor

Break down oversized epics into vertical user stories using Humanizing Work split patterns.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill epic-breakdown-advisor-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-breakdown-advisor
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/epic-breakdown-advisor
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill epic-breakdown-advisor-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large backlog items that are too big to estimate, sequence, or deliver safely stall delivery planning. This Skill splits epics into thin, end-to-end user stories while preserving user value in every slice, avoiding the trap of horizontal task decomposition. ## Core Features & Use Cases - INVEST Pre-Split Validation: Runs the INVEST checklist on the epic first, with an explicit stop when the item fails the Valuable check and must be reframed around user value. - Nine Ordered Split Patterns: Applies the Humanizing Work splitting patterns (workflow steps, operations, business rules, data variations, and more) in order, then proposes three candidate splits for the team to choose from. - Board-Ready Output: Emits story cards, a split evaluation report, and a flat CSV with a stable column contract for direct import into Jira or similar trackers. - Use Case: A team has an epic like "build the dispute state service" that cannot be estimated. The Skill reframes it around user value, proposes three splits, isolates a timeboxed spike for the open technical question, and exports the resulting stories as CSV. ## Quick Start Ask the assistant to break down your epic into user stories using the epic-breakdown-advisor, providing the epic text, the persona it serves, and why it is too large.

Frequently Asked Questions about epic-breakdown-advisor

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

FAQPage Schema
How do I split an epic into user stories?▼

Provide the epic in user-story form, the persona it serves, and why it is too large. The Skill validates it against INVEST, applies the nine Humanizing Work split patterns in order, and presents three candidate splits for you to choose from.

What are the Humanizing Work story splitting patterns?▼

They are nine ordered patterns: workflow steps, operations, business rule variations, data variations, data entry methods, major effort, simple/complex, defer performance, and break out a spike. Earlier patterns generally produce better vertical slices.

Can I import the split stories into Jira?▼

Yes. The Skill emits a flat CSV with a fixed column order: ID, Epic, Type, Summary, User Story, Acceptance Criteria, Priority, Release, Estimate, Dependencies, Labels. One row per story, ready for board import.

What happens if my epic fails the INVEST check?▼

If the epic fails the Valuable check, splitting stops. The item is a technical task, not a story, so the Skill reframes it around the user value it enables before any splitting continues.

When should I use a spike instead of splitting a story?▼

Use a spike only when genuine uncertainty blocks estimation, as the last of the nine patterns. Each spike gets a timebox and one specific question, with stated consequences for each possible answer.

Does the epic breakdown provide story point estimates?▼

No. It provides relative size signals only, such as T-shirt sizes, and flags anything over roughly five days for re-splitting. Absolute estimates in days or points remain the engineering team's responsibility.