decompose-plan

# Decompose Plan Skill

Transform implementation plans into structured, self-contained beads with proper epic groupings and dependencies.

## Your Role

**You are the decision-maker** for:
1. **Granularity** - How many beads? How big/small?
2. **Decomposition** - What work goes in each bead?
3. **Dependencies** - Which beads block which?
4. **Context Distribution** - What information each bead needs to be self-contained
5. **Epic Structure** - How to group related beads under epics

You are NOT just running `br create` commands—you're applying judgment to create a coherent, actionable task structure.

## Input Handling

**Expected input:** A file path to a plan document (e.g., `/path/to/plan.md`)

1. Validate the file exists using the Read tool
2. Parse the entire plan content
3. If file doesn't exist, report error and stop

## Analysis Phase

Before creating any beads, thoroughly analyze the plan:

### 1. Understand Business Context
- What problem does this solve?
- What are the project's overarching goals?
- Why does this matter?

### 2. Identify Natural Boundaries
Look for seams in the work:

| Boundary Type | Example |
|---------------|---------|
| Different files/modules | API routes vs middleware vs models |
| Different concerns | Auth logic vs token handling vs rate limiting |
| Sequential dependencies | Must have X before Y |
| Parallelizable work | Can do X and Y simultaneously |
| Phases/milestones | Phase 1: Setup, Phase 2: Core features |

### 3. Map Structure
- Identify phases → these become **epics**
- Identify tasks within phases → these become **beads**
- Note dependencies between tasks

## Decomposition Rules

### Granularity Guidelines

| Plan Complexity | Typical Beads | Epic Structure |
|-----------------|---------------|----------------|
| Tiny (1 file change) | 1 bead | No epic needed |
| Small (2-3 related files) | 2-3 beads | Maybe 1 epic |
| Medium (feature) | 4-8 beads | 1-2 epics |
| Large (system) | 8+ beads | Multiple epics, possibly nes