Blueprint

Phase 3: DEPENDENCY GRAPH

• Map which steps block which other steps
• Identify steps that can run in parallel (different files/modules)
• Mark the critical path

Phase 4: ADVERSARIAL REVIEW

• Challenge each step: "What could go wrong?"
• Check for missing steps (migrations, localization, tests, config)
• Verify the plan doesn't violate any architecture decisions in CLAUDE.md

Output Format

# Blueprint: [Feature Name]

## Objective
[One line]

## Steps

### Step 1: [Title]
**Context brief:** [Everything a fresh agent needs to know]
**Files:** [List of files to read/create/modify]
**Changes:** [Specific changes to make]
**Tests:** [What tests to write]
**Done when:** [Clear acceptance criteria]
**Blocks:** Step 2, Step 3

### Step 2: [Title]
**Blocked by:** Step 1
...

## Dependency Graph
Step 1 → Step 2 → Step 4
Step 1 → Step 3 → Step 4

## Parallel Opportunities
Steps 2 and 3 can run in parallel (different modules)

## Risks
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]

## Estimated Steps: N | Critical Path: Steps 1→2→4

Save the blueprint to docs/blueprints/[feature-name].md for future sessions.

$ARGUMENTS