Multi-Agent Orchestration (multi-agent-orchestration)

Coordinate multi-agent engineering workflows across parallel sub-agents operating in isolated git worktrees without branch collisions, resource contention, or unverified merges. This skill defines an orchestration protocol with pluggable verification hooks, compatible with Orca, OpenSpec, AgentMemory, and native CLI sub-agents.

When to Use

• Coordinating feature development, system refactors, component design, or companion backend/web services across parallel sub-agents
• Operating in Manual Mode (active user review for UI/UX changes, deployment notifications) vs. Automatic Mode (40-min inactivity fallback, 2-min single wait per delivered job)
• Running the Coordinator Cycle Workflow (sweep, check progress and merge, run the cycle, /cycle) to drain inbox messages, inspect workers, delegate validation, merge cleanly, run host smoke tests, and execute complete cleanup
• Naming, spawning, and timeboxing isolated git-worktree sub-agents
• Delegating non-trivial validation to lower-intelligence validation agents (Gemini Flash) with immediate teardown
• Triaging bugs (fix simple issues on the spot vs. send back to original worker), and managing feature-worker keep-alive windows for user feedback

1. Operating Modes, Wait Discipline & Keep-Alive Protocol

The Coordinator operates under one of two operating modes governing validation, merge gating, and worker lifecycles: