waves-codex

# 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 agents load in trusted projects only), and subagent limits live under `[agents]` in `config.toml`. Official docs no longer enumerate the collaboration tool names; the current (multi-agent V2) surface exposes `spawn_agent`, `send_message`, `followup_task`, `wait_agent`, `interrupt_agent`, and `list...