waveslisted

# Waves <!-- harness:claude-code --> In Codex, first read [Codex distribution](../delegation/references/dispatch-knobs.md#codex-distribution) for installed role setup, native dispatch, isolation prerequisites, and completion routing. That section supplies the Codex procedures wherever this workflow names Claude Code tools. <!-- /harness --> Run one session as a **backlog-execution loop**: orient from the handoff and the triage view, refresh the triage, plan items into waves, launch isolated crews, personally verify and land each wave, reconcile, and externalize — so the owner's only inputs are the launch prompt and the decisions that are genuinely theirs. This skill is the *campaign* layer. The **delegation** skill governs each wave's delegation architecture; the **handoff** skill closes the session. Waves adds what neither has: the triage view as the living plan, the wave-shaping rules, the landing queue, and the end-of-run externalization contract. ## The two artifacts 1. **The handoff** (per the handoff skill — a file in the repo, or an external tracker item when the project routes it there) — session bridge; carries owner rulings and gotchas. 2. **The triage view** — a curated, ranked view of the open backlog plus the current delivery plan, held wherever the tracker binding says. **The inventory is the source of truth; this is a view** — if they disagree, fix the view. ## The backlog seam Waves needs three operations from whatever tracks the work. Everythi