Parallel Builder: Divide-and-Conquer Implementation

Parallel Builder: Divide-and-Conquer Implementation

Decomposes a plan/spec into independent tasks, spawns builder agents to implement each piece in parallel, and integrates the results. Unlike feature-council (same task, diverse approaches), this skill gives each agent a different piece of the work for maximum speed.

Use this when you have a spec, PRD, or plan and want fast parallel implementation.

When to Use

✅ Use parallel-builder for:

• Implementing a PRD or spec document
• Large features that can be decomposed into parts
• When speed matters more than approach diversity
• Building from a reference file or detailed plan
• Multi-file implementations with clear boundaries

❌ Don't use for:

• Bugs (use debug-council)
• Features where you want diverse approaches (use feature-council)
• Tasks that can't be parallelized
• Simple single-file changes

Where Parallel-Builder Shines

🚀 Maximum Speedup: Multi-File Specs

Parallel-builder is fastest when your spec produces multiple independent files:

┌─────────────────────────────────────────────────────────────┐
│  IDEAL: Each agent owns different files                     │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Wave 2: TRUE PARALLEL EXECUTION                            │
│  ┌─────────────────┐ ┌─────────────────┐ ┌────────────────┐│
│  │ Agent 1         │ │ Agent 2         │ │ Agent 3        ││
│  │ userService.ts  │ │ authService.ts  │ │ apiClient.ts   ││
│  └─────────────────┘ └─────────────────┘ └────────────────┘│
│          ↓                   ↓                   ↓          │