agent-wavelisted

# agent-wave Drive the implementation queue with parallel subagents, in waves. ## Honest scope (read first) In-session subagents are bounded by **this session**, not by wall-clock hours. So this skill measures budget reliably in **items and waves**, with hours as a *soft cap* (stop starting new waves once elapsed time passes it). For a true multi-hour unsupervised fleet that outlives a session, use remote agents or a scheduled run of `_agent/prompts/autonomous.md` (`/schedule`) instead — this skill points you there rather than pretending to be it. ## Step 0 — Preconditions and context 1. Confirm the repo is bootstrapped with a `plan/` queue and that `_agent/prompts/autonomous.md` exists (a real verify gate is required — see the **bootstrap** skill, Q8). 2. Read `CONVENTIONS.md` for the **multi-agent mode** and **integration model**. - **Mode 1 (single agent):** refuse. Parallel agents in one checkout clobber each other. Tell the user to re-bootstrap as mode 2/3, or run the autonomous prompt sequentially instead. - **Mode 2 (shared checkout):** allowed but warn — file contention is real; LOCKS must be respected and wave width kept low. - **Mode 3 (worktrees):** the intended mode. Each subagent works in its own isolated worktree. ## Step 1 — Ask the wave parameters (one at a time, recommend) 1. **Wave width N** — how many agents per wave. *Recommended: min(queue depth, 3)* — modest, keeps review tractable. 2. **Budget** — total it