allconvos.ai
← All walkthroughs
Walkthrough — Workflow
Wave Execute
Parallel Plan Execution
Go from idea to shipped feature using brainstorm → plan → wave-execute. Tasks grouped by dependency, dispatched to fresh agents in parallel. No context rot.
The Pipeline
ce-brainstorm What to build + spec ce-plan Numbered tasks + deps /wave-execute Parallel fresh agents
The Problem: Context Rot
T1 T2 T3 T4 T5 T6 T7 Fresh Degraded Sequential execution: one agent accumulates 200K of context Quality degrades as context fills up
The Solution: Wave-Based Execution
Wave 1 — No dependencies (parallel) Agent A: Schema Agent B: Stripe sync Agent C: Auth middleware FRESH CONTEXT FRESH CONTEXT FRESH CONTEXT Wave 2 — Depends on Wave 1 (parallel) Agent D: Invoice API Agent E: PDF reports Agent F: Billing API FRESH CONTEXT FRESH CONTEXT FRESH CONTEXT Wave 3 — Depends on Wave 2 (parallel) Agent G: Dashboard Agent H: Invoice page Agent I: Billing page FRESH CONTEXT FRESH CONTEXT FRESH CONTEXT Wave 4 — Depends on all (sequential) Agent J: Integration tests FRESH CONTEXT
When to Use Which Flow
Task Size Flow Why
Trivial Just do it No plan needed
Small (1–4 tasks) ce-work Wave overhead not worth it
Medium–Large (5+) brainstorm → plan → /wave-execute Parallel agents, fresh contexts, no rot
Example: Building a Client Portal

Step 1: Brainstorm

Describe your idea. Claude asks questions one at a time — auth model, data source, scope, constraints. Produces a spec document.

> I want to add a client portal. Customers view invoices, download PDFs, update billing.
What authentication do customers use? → NextAuth email/password
Where does invoice data live? → Stripe
Separate app or existing? → Part of the Next.js app under /portal

Step 2: Plan

Claude produces a structured plan with 10 numbered tasks, file paths, and explicit dependencies between them.

Task 1: Database schema
Task 2: Stripe sync service
Task 3: Auth middleware
Task 4: Invoice API   ← depends on 1, 2
Task 5: PDF reports   ← depends on 2
Task 6: Billing API   ← depends on 1, 3
Task 7: Dashboard page   ← depends on 3, 4
Task 8: Invoice page   ← depends on 4, 5
Task 9: Billing page   ← depends on 6
Task 10: Integration tests   ← depends on 7, 8, 9

Step 3: Wave Execute

Type /wave-execute plan.md. Claude analyses dependencies and presents wave groupings. You approve, and parallel agents execute each wave with fresh contexts.

Wave Execution Plan
Wave 1: Tasks 1, 2, 3  — 3 parallel agents
Wave 2: Tasks 4, 5, 6  — 3 parallel agents
Wave 3: Tasks 7, 8, 9  — 3 parallel agents
Wave 4: Task 10       — sequential
10 tasks across 4 waves. Proceed? (yes / adjust / sequential)

Result

10 atomic commits, each from a fresh agent. Clean git history, no context rot, and your global skills (TDD, security review, verification) enforced on every task.

Skills That Carry Through
tdd-first systematic-debugging verification-before-completion security-review git-conventions code-quality
Every agent spawned by /wave-execute inherits your global skills. They don't just execute tasks — they execute them to your standards.