From jbb-feature-dev
Decompose a PRD, RFC, epic, or high-level initiative into independently-executable feature outlines using vertical slices. Each feature gets its own research pipeline run. Use when the input is too large or too high-level for a single research/plan cycle. Trigger phrases (1) "break down initiative" (2) "break down epic" (3) "split into features" (4) "break down PRD" (5) "PRD to features" (6) "break this down". Outputs to ~/.claude/thoughts/shared/decomposition/.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jbb-feature-dev:break-down-initiativeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break a high-level document (PRD, RFC, epic, initiative) into independently-executable
Break a high-level document (PRD, RFC, epic, initiative) into independently-executable feature outlines using vertical slices. Each output feature feeds into its own full pipeline run (research -> map-feature-to-plans -> plan -> implement).
Before proceeding, check whether this document is at the right abstraction level for strategic decomposition.
This skill is appropriate when the document describes WHAT to build — user stories, requirements, business goals, multiple subsystems or features.
This skill may not be appropriate when the document:
type: research)If the input looks like a single-feature research document, inform the user:
"This document appears to describe a single well-understood feature with implementation
details rather than a high-level initiative with multiple features. You may want to use
the map-feature-to-plans skill instead, which splits a single researched feature into
implementation plans."
Non-interactive: log the observation and proceed if the document has >=2 distinct subsystems/features. Otherwise, output a single-feature pass-through.
Parse $ARGUMENTS for flags and input:
--non-interactive: Auto-approve all decisions using ~/.claude/skills/decision-principles/SKILL.md. Log each decision. File path argument is REQUIRED.Read the PRD/RFC/epic document FULLY (no limit/offset). If the user provides URLs (Google Docs, Jira, Slack), use ToolSearch to discover relevant MCP tools and fetch the content.
Identify from the document:
Spawn a codebase-explorer agent to understand the current architecture, components, and domain boundaries in the target repository.
The codebase knowledge helps identify which integration layers each vertical slice must cross. Slice by user value, NOT by code module. The architecture informs the slicing but does not drive it -- a feature should never be "refactor the database layer" (horizontal).
Non-interactive: proceed automatically after agent completes.
Read references/splitting-criteria.md for the strategic splitting criteria.
For each identified feature, produce an outline:
Prefer many thin slices over few thick ones. Prefer AFK over HITL where possible.
Non-interactive: draft slices and proceed to Step 5.
Present the proposed breakdown as a numbered list showing title, type, blocked-by, and user stories for each feature.
Ask the user:
Iterate until the user approves the breakdown.
Non-interactive: skip this step. Auto-approve using decision-principles, log decisions.
Read references/output-template.md for the document structure.
~/.claude/thoughts/shared/decomposition/ directory if it does not exist.YYYY-MM-DD-<kebab-case-description>.mdFor each feature outline, suggest the next pipeline command:
Feature 1 [AFK]: /research-problem "Feature 1 description"
Feature 2 [HITL]: Needs human decision on [X] before research
Feature 3 [AFK]: /research-problem "Feature 3 description" (blocked by Feature 1)
references/splitting-criteria.md -- Read in Step 3. Contains 4-5 strategic
splitting criteria with concrete examples for PRD-to-feature decomposition.references/output-template.md -- Read in Step 5. Contains the decomposition
document template with YAML frontmatter and section structure.npx claudepluginhub jonnycbb/claude-code-config --plugin jbb-feature-devThis skill should be used when the user asks to "break down this initiative", "decompose into tasks", "create tasks from initiative", "how to size tasks", "when to decompose", "vertical slices", "task granularity", or needs guidance on breaking higher-level work into lower-level work items.
Decomposes specification documents into independent changes using outline, section, or hierarchical modes with dependency graphs and independence scores.
Analyzes PRD into atomic features with Gherkin acceptance criteria, performs product/architecture/QA analysis, generates dependency graphs, MVP features, and project plans from specs.