team-orchestration

Multi-agent coordination for code review uses a TeamCreate-driven workflow to spawn persistent coder, reviewer, and committer agents. These agents collaborate through inter-agent messages to deliver implementation tasks rather than relying on manual handoffs.

Task decomposition with dependencies splits an implementation request into ordered subtasks routed to specific agents. The orchestrator manages these dependencies, unblocking subsequent tasks only after previous agent verdicts like APPROVED or FIX_REQUIRED are received.

To set up a coder, reviewer, and committer team, describe your implementation task and let the orchestrator assemble the team. It handles agent spawning, message routing for verdicts, fix loops, and complete shutdown cleanup after reporting results.

The orchestrator never performs coding, reviewing, or committing directly. It enforces pure delegation, meaning all actual implementation work and code review tasks are delegated to the spawned persistent agents through message-driven routing.

When a reviewer agent rejects code with a FIX_REQUIRED message, the orchestrator manages a fix loop by routing the verdict back to the coder agent. This cycle continues until the code is approved, at which point dependencies unblock and the committer agent proceeds.

Message-driven agent orchestration is ideal for multi-role development scenarios requiring persistent coder, reviewer, and committer collaboration. Use it when you need clear separation between planning and execution, automatic dependency management, and structured lifecycle shutdown.