waves
WAVES — Workers · Aggregate · Verify · Extend — wave-based orchestration for Cursor. Decompose a big goal into independent slices, fan them out to isolated parallel subagents via parallel Task tool calls as a bounded "wave", verify each structured handoff, then synthesize, and extend into another wave only when warranted. Invoke explicitly with /waves; bounded by design to avoid runaway token loops. For big research, analysis, audits, and codebase or data exploration where one linear pass is slow. Formerly parallel-orchestrate; also fan out, parallelize, orchestrate subagents, multi-agent.
npx skills add RayFernando1337/rayfernando-skills --skill waves --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 spa
- When to use
- When to skip
- Core principles
- Entropy-first decomposition
- The loop
- Step 0 — Discover first (serial, in the main session)
- Step 0.5 — Stage the data (when it's remote or messy)
- Step 0.7 — Triage: size the run, then classify each slice
- Step 1 — Decompose into independent slices
- Step 2 — Fan out in parallel
- Step 3 — Collect and synthesize
- Step 3.5 — Verifier pass (when the tier demands it)
- Step 4 — Second waves (continuous motion)
- Step 5 — Deliver
What does the waves skill do?
WAVES — Workers · Aggregate · Verify · Extend — wave-based orchestration for Cursor. Decompose a big goal into independent slices, fan them out to isolated parallel subagents via parallel Task tool calls as a bounded "wave", verify each structured handoff, then synthesize, and extend into another wave only when warranted. Invoke explicitly with /waves; bounded by design to avoid runaway token loops. For big research, analysis, audits, and codebase or data exploration where one linear pass is slow. Formerly parallel-orchestrate; also fan out, parallelize, orchestrate subagents, multi-agent.
How do I install it?
Run `npx skills add RayFernando1337/rayfernando-skills --skill waves --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From RayFernando1337/rayfernando-skills, a repository with 117 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.