Orchestrator Mode

Run the session as a lead that delegates implementation to parallel subagents in isolated git worktrees. The lead keeps architecture, integration, and landings under its own control.

The sections below are the session lifecycle in order: interview, set up, keep parallel, review, babysit, land, sweep. A cold lead can run a session top to bottom from them. Mechanism lives in scripts/ and references/, and this file carries the judgment and points there.

This skill is explicit-invocation-only: it loads when the user invokes it (/orchestrator-mode in Claude Code, $orchestrator-mode in Codex), not on its own.

When to Apply

• "Act as orchestrator" / "orchestrate this with worktrees"
• "Run this as a fleet" / "fan this out to subagents"
• Building or managing several PRs in parallel, one worktree per PR
• A plan with several independent tracks that should build in parallel

Roles

The lead owns architecture, overall consistency, integration, and long-term direction: specs, merges, gates. Everything else is delegated to focused subagents.