waves-codex
WAVES - Workers, Aggregate, Verify, Extend - wave-based orchestration for Codex. Decompose a big goal into independent slices, verify coverage, spawn Codex subagents in parallel as a bounded wave, collect evidence-backed handoffs, verify important claims, synthesize one deliverable, and extend into another wave only when warranted. Bounded by design to avoid runaway token loops; invoke deliberately. Formerly parallel-orchestrate-codex; also fan out, parallelize, spin up multiple agents, orchestrate workers, multi-stream research, audit a repo, split disjoint implementation work.
npx skills add RayFernando1337/rayfernando-skills --skill waves-codex --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# WAVES — Workers · Aggregate · Verify · Extend (Codex) Run **wave-based orchestration** with Codex subagents. A **wave** is a bounded round of isolated workers in parallel, then a round that verifies what came back, then a deliberate decision to build on it — not an open-ended loop. Use this skill when a task is too broad for one clean linear pass but can be split into independent slices. You are the manager: discover the problem shape, stage and verify coverage, decompose it, spawn bounded Codex workers, collect one structured handoff from each worker, verify important claims, and synthesize the final deliverable. **The shape of every wave — WAVE:** Workers fan out across disjoint slices -> Aggregate their handoffs -> Verify the evidence (the moat) -> Extend into another wave only when warranted. A loop doesn't know when to stop; a wave does, because verification is the stop function. (Invoke deliberately - a run spawns more agents than usual.) Current Codex docs checked on 2026-07-19: Codex subagents are enabled by default in current releases, built-in roles include `default`, `worker`, and `explorer`, custom agents live in `~/.codex/agents/` or `.codex/agents/` (TOML; project a
- When to Use
- When to Skip
- Core Principles
- Bounded Waves - Size, Budget, and the Stop Function
- Entropy-First Decomposition
- The Loop
- Step 0 - Discover Serially
- Step 0.5 - Stage and Verify Coverage
- Step 1 - Decompose into Independent Slices
- Step 2 - Fan Out with Codex Subagents
- Step 3 - Collect and Verify Handoffs
- Step 3.5 - Spawn Verifier Passes When Needed
- Step 4 - Second Waves (continuous motion)
- Step 5 - Deliver One Synthesized Artifact
What does the waves-codex skill do?
WAVES - Workers, Aggregate, Verify, Extend - wave-based orchestration for Codex. Decompose a big goal into independent slices, verify coverage, spawn Codex subagents in parallel as a bounded wave, collect evidence-backed handoffs, verify important claims, synthesize one deliverable, and extend into another wave only when warranted. Bounded by design to avoid runaway token loops; invoke deliberately. Formerly parallel-orchestrate-codex; also fan out, parallelize, spin up multiple agents, orchestrate workers, multi-stream research, audit a repo, split disjoint implementation work.
How do I install it?
Run `npx skills add RayFernando1337/rayfernando-skills --skill waves-codex --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.