Breaks down a feature into shippable chunks with dependencies mapped
4-6 hrs → 10 min
Compared to doing it manually
/feature-decomposition-toolType this in Claude to run the skill
PRDs get approved but engineering asks "how do we break this into sprints?" Without decomposition, estimates are wild guesses and dependencies bite you mid-build.
.claude/skills/ folder in your project/feature-decomposition-tool in Claude to run the skillCreates a quarterly plan with themes, bets, and resource allocation
Prioritizes your backlog using RICE, ICE, or custom frameworks
Creates a structured product roadmap from your goals, constraints, and priorities
Generate your daily plan aligned to goals and priorities. Start every day knowing exactly what to focus on.
Feature decomposition breaks large features into smaller, shippable increments. It enables faster delivery, reduces risk, and allows for learning along the way. Think "vertical slices" not "horizontal layers."
Small enough to ship in 1-2 sprints, but large enough to deliver user value. Each increment should be functional — avoid splitting into "backend only" or "UI only" pieces that don't work alone.
MVP is the minimum viable product — the smallest thing that validates your idea. Decomposition is how you break any feature (MVP or not) into increments. MVP answers "what to build first"; decomposition answers "how to build it iteratively."
Download this skill and drop it in your .claude/skills/ folder.
This skill + 70+ more, context files, and agent workflows — $499