Epic Breakdown Advisor
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
Install
npx skills add deanpeters/Product-Manager-Skills --skill epic-breakdown-advisorgit clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git /tmp/Product-Manager-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Product-Manager-Skills/skills/epic-breakdown-advisor ~/.claude/skills/epic-breakdown-advisorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Purpose Guide product managers through breaking down epics into user stories using Richard Lawrence's complete Humanizing Work methodology—a systematic, flowchart-driven approach that applies 9 splitting patterns sequentially. Use this to identify which pattern applies, split while preserving user value, and evaluate splits based on what they reveal about low-value work you can eliminate. This ensures vertical slicing (end-to-end value) rather than horizontal slicing (technical layers). This is not arbitrary slicing—it's a proven, methodical process that starts with validation, walks through patterns in order, and evaluates results strategically. ## Input **Works best with:** The epic or large story you need to break down — paste it as written in your backlog. **Also useful:** Team context (sprint length, estimation ceiling) and what's blocking delivery (too big to estimate, sequence, or release). Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The advisor opens by asking for the epic text, then walks the Humanizing Work pattern flowchart against it. **Example invocation:** `Break this down: 'As a finance admin, I can export any report to Excel, PDF, or CSV with custom date ranges and saved templates.'` ## Key Concepts
Details
- Skill name
epic-breakdown-advisor- Repository
- deanpeters/Product-Manager-Skills
- Path
skills/epic-breakdown-advisor/SKILL.md- Repo updated
- 16 October 2026
FAQ
What does the Epic Breakdown Advisor skill do?
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
How do I install the Epic Breakdown Advisor skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add deanpeters/Product-Manager-Skills --skill epic-breakdown-advisor. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Epic Breakdown Advisor popular?
It lives in deanpeters/Product-Manager-Skills, which has 7,800 GitHub stars and 940 forks, and is included in 3 curated skill lists.
Related skills
Acquisition Channel Advisor
7.8kdeanpeters/Product-Manager-Skills
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
AI Shaped Readiness Advisor
7.8kdeanpeters/Product-Manager-Skills
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Altitude Horizon Framework
7.8kdeanpeters/Product-Manager-Skills
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Executive Onboarding Playbook
7.8kdeanpeters/Product-Manager-Skills
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
Discovery Process
7.8kdeanpeters/Product-Manager-Skills
Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.
Positioning Statement
7.8kdeanpeters/Product-Manager-Skills
Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.