epic-breakdown-advisor
by deanpetersepic-breakdown-advisor is a guided project management skill for breaking large epics into vertical user stories with Humanizing Work split patterns. It helps product managers choose the right split, preserve end-to-end user value, and remove low-value work before planning.
This skill scores 78/100, which means it is a solid listing candidate with useful workflow value for product managers and agents handling large epics. Directory users can reasonably expect better-than-generic guidance for splitting backlog items into user stories, though they should still want clearer adoption aids and supporting assets before relying on it for complex edge cases.
- Strong triggerability: the frontmatter and scenarios clearly target epic/story splitting, including example prompts like onboarding, reporting, and admin workflows.
- Good operational depth: the skill body is substantial (22,083 chars) with 11 H2s, 38 H3s, and workflow/constraint signals that suggest real stepwise guidance rather than a stub.
- Agent leverage is explicit: it promises Humanizing Work split patterns, vertical slicing, and evaluation of low-value work to remove, which is more actionable than a generic brainstorming prompt.
- No install command, scripts, references, or support files are included, so users get the workflow text but not external validation or automation hooks.
- The repository evidence shows the skill content itself, but directory users may still need to inspect the full document to understand the 9-pattern sequence and how strictly it is enforced.
Overview of epic-breakdown-advisor skill
epic-breakdown-advisor is a guided product management skill for splitting large epics into smaller, deliverable user stories using the Humanizing Work pattern set. It is most useful when a backlog item is too broad to estimate, sequence, or ship safely, and you need a structured way to preserve end-to-end user value instead of slicing by technical layer.
Who this skill is for
The epic-breakdown-advisor skill is a strong fit for product managers, PMs working with design and engineering, and anyone preparing sprint-ready stories from a vague feature request. It is especially helpful for epic-breakdown-advisor for Project Management when the main problem is not ideation, but turning a messy epic into a coherent delivery plan.
What it helps you decide
This skill helps you choose the right splitting pattern, test whether a split still delivers value, and spot low-value work that can be removed altogether. The real job-to-be-done is not “make items smaller”; it is “make items small enough to plan while keeping them meaningful.”
Why it is different
Unlike a generic prompt that just asks for “smaller stories,” epic-breakdown-advisor follows a deliberate sequence of splitting patterns and emphasizes vertical slices. That matters when teams accidentally create horizontal splits like frontend-only or backend-only work, which are easier to name but harder to deliver incrementally.
How to Use epic-breakdown-advisor skill
Install and locate the source
Use the repository skill install path and load the skill from skills/epic-breakdown-advisor:
npx skills add deanpeters/Product-Manager-Skills --skill epic-breakdown-advisor
After install, start with SKILL.md. In this repository, that is the only source file, so there is no separate README.md, rules/, or scripts/ layer to cross-check.
Give the skill the right input
For best epic-breakdown-advisor usage, start with the epic itself, the target user, and the delivery constraint. A strong input names the feature, the user outcome, and what makes the epic too large.
Example prompt shape:
“Split this onboarding epic into sprint-sized user stories. The goal is to let a new user complete setup in under 5 minutes. Keep the slices vertical, identify the best split pattern, and flag any work that can be removed.”
Read the output as a workflow
The epic-breakdown-advisor guide is designed to help you apply a pattern, not just accept a list. Read the recommendation in this order: pattern choice, rationale, resulting story slices, then any notes on value preserved or work eliminated. If the output skips the why, ask for the split logic before you move stories into planning.
Use it well in your planning process
Best results come when you run the skill before estimation and before engineering has already committed to a technical decomposition. Feed it one epic at a time, include known constraints like release scope or dependencies, and ask for slices that can be validated independently by users or stakeholders.
epic-breakdown-advisor skill FAQ
Is this just a better prompt?
No. The epic-breakdown-advisor skill is useful because it gives you a repeatable splitting method, not just a one-off suggestion. If you already know the exact split pattern you want, a plain prompt may be enough; if you need help choosing the pattern, this skill is better.
Does it work only for product managers?
It is built for PM workflows, but it can also help analysts, delivery leads, and engineering managers who need clearer backlog shaping. If you are not managing product delivery decisions, you may find the method useful but heavier than necessary.
When should I not use it?
Do not use epic-breakdown-advisor when the work is already small, when the request is purely technical refactoring, or when the goal is brainstorming rather than delivery planning. It is strongest when there is a real epic that needs structured decomposition.
Is it beginner-friendly?
Yes, if you can describe the user outcome and the epic boundaries. You do not need to know the Humanizing Work patterns in advance, but you will get better results if you can answer what user value must stay intact in every slice.
How to Improve epic-breakdown-advisor skill
Provide sharper epic boundaries
The biggest quality gain comes from stating what is in scope, what is out of scope, and which user journey matters most. epic-breakdown-advisor performs better when you say “new customer onboarding” than when you say “improve the dashboard,” because the former has a clearer value path to preserve.
Ask for vertical slices explicitly
If your first output looks too technical, ask the skill to reslice it around user-visible outcomes, not components. Say that you want each story to be independently valuable, testable, and releasable, and that horizontal splits are a failure mode.
Iterate on the pattern, not just the list
When the first breakdown is close but not quite right, ask which splitting pattern was chosen and why the other patterns were rejected. That helps you adjust the decomposition logic instead of merely renaming stories, which is where better epic-breakdown-advisor usage usually comes from.