orchestrate

# Multi-Agent Orchestration ## Standalone Codex Skip every Claude heavy-skill marker in this file. Create each bounded worker with `spawn_agent`, deliver context to a running worker with `send_message`, trigger another turn for an idle existing worker with `followup_task`, wait with `wait_agent`, and stop a current turn with `interrupt_agent` only when necessary. Never spawn `codex-verifier` or call `codex-run.ts`. Read the live concurrency limit and stay within it. Writers share the working tree unless the live host explicitly offers isolation. Assign non-overlapping ownership and serialize implementer and test-writer phases; only read-only reviewers may overlap. Codex implementers are not promised Claude worktree isolation. **Claude-only marker:** standalone Codex must skip this command. `mkdir -p ~/.claude/tmp && echo "orchestrate" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` ## Phase 1: Research & Feasibility (GO/NO-GO Gate) Before delegating to agents: 1. **Parse requirements** - Break down what needs to happen 2. **Identify workstreams** - Which are independent? Which have dependencies? 3. **Assess scope** - Is this actually multi-agent work, or simpler than it looks? 4. **Sort into two piles** (the Orchestration Tax — your review attention is the serial bottleneck and it doesn't parallelize): - **Delegate-async** — isolated, well-specified work where your judgment lands at the *gate* (you review the ...