From decaf-planning
Break a plan phase (epic) into implementable features with acceptance criteria. Use when user wants to decompose a phase before starting implementation, break an epic into features, or detail a vertical slice into work items.
How this skill is triggered — by the user, by Claude, or both
Slash command
/decaf-planning:breakdown-phaseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break a single phase from a plan into implementable features. Each feature is an independently buildable and reviewable chunk of work. Does NOT break features further into tasks — that happens at implementation time.
Break a single phase from a plan into implementable features. Each feature is an independently buildable and reviewable chunk of work. Does NOT break features further into tasks — that happens at implementation time.
Locate the phase to break down. The user may provide:
./plans/feature-name.md)If the phase is not clear, ask the user to specify which phase they want to break down.
Also locate the parent plan (root work item or plan file) to pull in:
Explore the codebase to understand its current state — not the state when the plan was created. Earlier phases may have already been implemented, changing the landscape.
Focus on:
Skip this step if the codebase was already explored in this conversation and no implementation has happened since.
Break the phase into features. Each feature should be:
For each feature, draft:
Present the proposed features as a numbered list. For each feature show:
Ask the user:
Iterate until the user approves.
@../../../../conventions/work-items.md
Detect the available system and confirm with the user. If the parent phase already exists as a work item, use the same system.
Create one work item per feature as children of the phase.
Work item type mapping:
| System | Phase type | Feature type |
|---|---|---|
| Beans | epic | feature |
| GitHub Issues | Issue (sub-issue of plan) | Sub-issue of phase |
| Azure DevOps | Epic or Feature | Feature or User Story |
| Markdown | Section in plan file | Subsection under phase |
Each feature work item contains:
<Feature title>For markdown output, append features under the phase section in the plan file:
### Feature N.1: Dependencies: None | Feature N.2, Feature N.3<Description of what to build — end-to-end behavior.>
After creating features, update the parent phase work item (or plan section) to include a checklist of the created features with links/IDs, so progress can be tracked at the phase level.
/decaf-planning:breakdown-phase 2 # Break down phase 2 from plan in context
/decaf-planning:breakdown-phase ./plans/auth.md#3 # Phase 3 from a plan file
/decaf-planning:breakdown-phase BEAN-42 # Break down a beans epic
npx claudepluginhub alphaleonis/decaf-claude-config --plugin decaf-planningDecomposes large features into concrete, self-contained development phases with DAG dependencies. Each phase delivers testable code; outputs YAML manifest.
Generates structured phased implementation plans from feature descriptions, sized for 30-50k token sub-agent contexts, with clarifying questions, acceptance criteria, and dependencies. Invoke before multi-phase execution.
Decomposes feature requests into phased task boards with dependency mapping, parallelization flags, risk flags, edge cases, and test matrices.