team-orchestration

name	team-orchestration
description	6-phase multi-agent pipeline with approval gates. Orchestrates Plan→Design→Implement→Review→Test→Deploy phases with explicit entry/exit criteria, phase-level agent assignment, and human-in-the-loop approval checkpoints.
version	1.0.0
model	sonnet
invoked_by	both
user_invocable	true
tools	["Read","Write","Edit","Bash","TaskUpdate","TaskList","TaskCreate","TaskGet","Skill"]
agents	["master-orchestrator","planner","architect","developer","qa","devops","code-reviewer"]
category	Planning & Architecture
tags	["orchestration","pipeline","multi-agent","approval-gates","phases","team","workflow"]
best_practices	["Always define entry/exit criteria for each phase before spawning agents","Require human approval at Plan→Design and Review→Deploy transitions","Track phase state in .claude/context/plans/ for resumability","Never advance to the next phase without explicit exit criteria verification"]
error_handling	strict
source	builtin
trust_score	100
provenance_sha	afba8c1693518474

Team Orchestration

Overview

This skill provides a structured 6-phase multi-agent pipeline for medium-to-large feature work:

Plan → Design → Implement → Review → Test → Deploy

Each phase has:

• Entry criteria: conditions that must be met to start the phase
• Exit criteria: verifiable outputs that must be produced to leave the phase
• Approval gate: human or automated checkpoint before advancing
• Agent assignment: the specialist agent responsible for this phase

When to Use

Use for:

• Features that require collaboration across 3+ agents
• Work that spans multiple files and subsystems
• Tasks where quality gates between phases are important
• Enterprise deliveries requiring audit trail of phase transitions

Do NOT use for:

• Single-file bug fixes (use developer directly)
• Simple Q&A or documentation-only changes
• Tasks estimated under 1 hour

The Iron Law

NO PHASE ADVANCE WITHOUT VERIFIED EXIT CRITERIA

The orchestrator must verify every exit criterion before spawning the next phase's agent. If any criterion is unmet, the current phase remains active.

Phase Definitions

Phase 1: Plan

Entry criteria:

• User request received and understood
• Scope boundaries defined (in/out of scope)

Assigned agent: planner

Actions:

# Planner produces implementation plan
node .claude/tools/team-orchestration/team-orchestration.cjs --phase plan --task "{{task_description}}"

Exit criteria (ALL must pass):

• Implementation plan written to .claude/context/plans/{{task-id}}-plan.md
• Task decomposition lists ≥2 and ≤10 subtasks
• Risk/dependency section populated
• Plan reviewed by planner for completeness