// Multi-agent orchestration patterns for Claude Code team mode. Use when coordinating teammates, decomposing complex tasks, or managing shared task lists.
Setup guide for essential MCP servers. Use when configuring MCP servers or when user asks about search, SQLite, or MCP management.
Query Claude Code session analytics from ccrecall database. Use when user asks about token usage, session history, or wants to analyze their Claude Code usage patterns.
High-leverage prompts that challenge Claude's defaults. Use for "grill me", "prove it works", "scrap this", "what would 10x engineer do", "find ways this fails".
Maintain CLAUDE.md files effectively. Use when adding lessons learned, updating conventions, or restructuring project instructions.
Enhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints.
Terminal setup for Claude Code. Use for Ghostty config, statusline customization, voice dictation, tmux worktrees.
| name | orchestration |
| description | Multi-agent orchestration patterns for Claude Code team mode. Use when coordinating teammates, decomposing complex tasks, or managing shared task lists. |
Patterns for coordinating multi-agent work in Claude Code using team mode.
Source: code.claude.com/docs/en/agent-teams
Tell the lead what team you want in natural language:
Create an agent team to refactor the auth module. Spawn three teammates:
- One focused on extracting shared utilities
- One migrating tests to the new structure
- One updating documentation
Use Sonnet for each teammate.
The lead creates the team, spawns teammates, distributes work via a shared task list, and synthesizes results.
| Component | Role |
|---|---|
| Team lead | Your main session — creates team, spawns teammates, coordinates |
| Teammates | Separate Claude Code instances working on assigned tasks |
| Task list | Shared work items teammates claim and complete |
| Messaging | SendMessage for DMs, broadcasts, and shutdown requests |
Teammates are persistent — they go idle between turns and can be woken up with messages. They can message each other directly.
| Subagents | Teams | |
|---|---|---|
| Communication | Report back to caller only | Message each other directly |
| Coordination | Main agent manages all work | Shared task list, self-coordination |
| Best for | Focused tasks, only result matters | Complex work needing collaboration |
| Token cost | Lower | Higher (each teammate = separate instance) |