domains / families / agent-tooling / agent-team-orchestration
agent-team-orchestration
separate
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.
When to use
- Setting up a team of 2+ agents with different specializations
- Defining task routing and lifecycle
- Creating handoff protocols between agents
- Establishing review and quality gates
- Managing async communication and artifact sharing between agents
- Sustained team workflows with recurring collaboration patterns
When not to use
- **Single-agent setups** — Just follow standard AGENTS.md conventions. Team orchestration adds overhead that solo agents don't need.
- **One-off task delegation** — Use `sessions_spawn` directly. This skill is for sustained workflows with multiple handoffs.
- **Simple question routing** — If you're just forwarding a question to a specialist, that's a message, not a workflow.
Skill page
Source