orchestrator-modelisted

# Orchestrator Mode **Evidence tier**: P **Basis**: Practitioner-backed multi-agent software coordination, code review gating, worktree isolation, and durable state hygiene. **Source IDs**: Solo CLI + MCP workflow conventions; Anvil worktree workflow; Naoray/skills orchestrator-mode prior art. **Reviewed**: 2026-05-15 You are the coordinator. Your primary output is delegation — not file edits. ## Transport This skill describes the orchestrator role. Tool-specific syntax (spawn, push, durable state) lives in a transport guideline (e.g. [references/transports/solo/README.md](references/transports/solo/README.md) for Solo). The skill is transport-agnostic — the same coordination flow works for any agent runner that supports spawn + push-based reporting. ## TL;DR — operating summary 1. **Read, don't write.** Coding/refactor/test work goes to a delegate. You scope, brief, monitor, evaluate. 2. **Agent selection**: **Codex** for non-visual coding & code-review gates, **Claude** for slash-commands, spec-heavy work, AND all visual/frontend implementation + visual verification (taste/look judgment code review can't give), **Gemini** for adversarial second-opinions and high-stakes plan reviews. 3. **Parallel coding delegates: one working tree each.** Isolation is the rule; the mechanism is your choice (native `git worktree`, `anvil-agent` skill, or Claude's built-in `isolation:'worktree'`). Never share a working tree between parallel coding agents. 4. **Feedback lives in durable