| layout | title | nav_order | parent | checklist_enabled | checklist_stage | checklist_section | checklist_order | checklist_audit_areas | |
|---|---|---|---|---|---|---|---|---|---|
default |
Agent Teams |
5 |
Tool Guides |
true |
stage-5 |
Tool-Fit Checklist |
5 |
|
A single agent can execute many tasks, but complex work often benefits from multiple specialists coordinating: architecture, implementation, QA, and documentation.
Agent teams help when:
- the task spans multiple disciplines
- you need parallel work with role-specific quality bars
- one coordinator should keep global constraints while specialists execute
This makes "agents talking to each other" explicit and structured instead of ad hoc.
Agent teams are an experimental Claude Code feature. Enable them by setting CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in the environment where Claude Code runs.
Use natural-language delegation in chat to involve teammates for specialized work.
Important clarification:
- there is no separate
.claude/agents/team/team-manifest path - there is no
/agents-teamcommand
Use settings and prompts to shape collaboration behavior, and pair teams with custom agents when you need reusable specialist roles.
Start with three roles:
- Coordinator — owns goals, constraints, and final synthesis
- Builder — implements changes and reports verification
- Reviewer — validates risks, regressions, and policy alignment
Add more roles only when repeated bottlenecks appear.
Use sub-agents when one primary agent can still coordinate effectively and you only need targeted delegation.
Use agent teams when collaboration itself is the core challenge and role boundaries should be persistent.
Too many roles too early. Start lean; scale roles from real pain points.
Role overlap. If two teammates own the same decision, accountability becomes unclear.
No integration checkpoints. Require merge checkpoints and explicit handoffs.