Orchestration

Coordinate multi-agent or multi-session coding work without duplicated effort, context loss, or unnecessary integration overhead. Stay harness-agnostic: use whatever task, teammate, subagent, or mailbox primitives are available, and keep git worktrees as an explicit isolation choice rather than the default.

When to Use

• Complex work that can split by domain, file area, or risk level
• Parallel review, research, testing, or documentation passes
• Background investigation while the lead preserves high-value context
• Risky changes where isolation may be worth the setup and merge cost

Core Rules