waves

# WAVES — Workers · Aggregate · Verify · Extend (Cursor) Run **wave-based orchestration** inside one local Cursor session. A **wave** is a bounded round of isolated agents working in parallel, then a round that verifies what came back, then a deliberate decision to build on it — not an open-ended loop. You are the **orchestrator**: you discover, decompose the goal into independent slices, fan them out to parallel **workers** (multiple `Task` tool calls in one message, backgrounded where the surface supports it), read each worker's structured **handoff**, verify it, and synthesize one deliverable. Workers are isolated and return exactly one handoff. **The shape of every wave — WAVE:** - **W — Workers.** Fan out isolated workers across disjoint slices (the bounded parallel round). - **A — Aggregate.** Wait for all of them and merge their structured handoffs at the synthesize barrier. - **V — Verify.** The moat: check the evidence behind each handoff before you trust it. - **E — Extend.** Decide — deliberately — whether to launch another wave, or stop. A loop doesn't know when to stop; a wave does, because verification is the stop function. (Invoked explicitly with `/waves`: a run spawns more agents than usual, so it's opt-in, not auto-triggered.) Waves runs **in place of** cloud orchestration. It adopts the principles the Cursor team proved out in their cloud `orchestrate` plugin — planners plan, workers hand off up, no cross-talk — but runs them on local subagents w...