orchestration
Multi-agent orchestration patterns for Claude Code team mode. Use when coordinating teammates, decomposing complex tasks, or managing shared task lists.
What this skill does
# Orchestration Patterns for coordinating multi-agent work in Claude Code using team mode. Source: [code.claude.com/docs/en/agent-teams](https://code.claude.com/docs/en/agent-teams) ## Quick Start Tell the lead what team you want in natural language: ```text 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. ## How It Works | 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. ## Key Behaviours - **Lead spawns teammates** based on your prompt — you describe the team, the lead creates it - **Teammates self-claim tasks** from the shared list after finishing work - **No nested teams** — teammates cannot spawn their own teams or teammates - **File partitioning** — never assign the same file to multiple teammates - **3-5 teammates** is the sweet spot for most workflows - **5-6 tasks per teammate** keeps everyone productive ## When Teams vs Subagents | | 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) | ## References - [patterns.md](references/patterns.md) - 6 orchestration patterns (fan-out, pipeline, map-reduce, speculative, background, task-graph) - [domains.md](references/domains.md) - 8 domain-specific decomposition guides - [task-management.md](references/task-management.md) - Task dependencies, graph walking, file partitioning
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.