wave-execution

Wave-Based Parallel Execution

Problem: Sequential execution wastes time on independent tasks.

Solution: Group tasks into waves based on dependencies. Execute waves sequentially, tasks within waves in parallel.

---

When to Use

Multiple tasks in implementation plan?
        ↓ YES
WAVE EXECUTION ← APPLY

Use when:

• 2+ independent tasks in implementation plan
• Tasks have clear dependency relationships
• Parallel execution provides clear speedup
• Subagents available for parallel dispatch

Don't use when:

• Single sequential task
• Tasks deeply interdependent (must run sequentially)
• No subagent dispatch capability
• Time not critical (efficiency not priority)

---

Wave Resolution Algorithm

Dependency Analysis

## TASK DEPENDENCY MATRIX

Tasks:
T1: Create user model
T2: Create user API (depends on T1)
T3: Create auth API (depends on T1)
T4: Create checkout API (depends on T2, T3)
T5: Create payment API (depends on T4)
T6: Create email notification (depends on T2)

Dependency Graph:
T1 → [T2, T3]
T2 → [T4, T6]
T3 → [T4]
T4 → [T5]
T6 → []

Wave Classification

Wave	Tasks	Reason	Parallel?
Wave 1	T1	No dependencies	No (single task)
Wave 2	T2, T3	Depend only on T1	YES
Wave 3	T4, T6	Depend only on Wave 2	YES
Wave 4	T5	Depend on T4	No (single task)

Wave Resolution Output

## WAVE RESOLUTION

Wave 1 (Sequential):
└── T1: Create user model

Wave 2 (Parallel):
├── T2: Create user API
└── T3: Create auth API

Wave 3 (Parallel):
├── T4: Create checkout API
└── T6: Create email notification

Wave 4 (Sequential):
└── T5: Create payment API

Total: 6 tasks → 4 waves
Parallelization: 2.0x speedup (vs sequential)

---

Execution Protocol

Pre-Execution Checklist

□ All tasks identified and documented?
□ Dependencies mapped?
□ Wave boundaries determined?
□ File ownership assigned per task?
□ Parallel safety verified (no file conflicts)?
□ Sequential dependencies enforced?
□ Budget allocated per wave?
□ Verification checkpoints set?