AgentSkillsCN

orchestrating

熟练运用Claude Code的代理团队与任务系统,掌握多代理编排技巧。适用于协调多个代理、并行开展代码审查、构建带依赖关系的流水线工作流、打造自组织任务队列,或任何受益于分而治之模式的任务。还可路由至专门的子技能,涵盖团队管理、任务、消息传递、模式、后端与错误处理。

SKILL.md
--- frontmatter
name: orchestrating
description: Master multi-agent orchestration using Claude Code's agent teams and task system. Use when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns. Routes to specialized sub-skills for team management, tasks, messaging, patterns, backends, and error handling.

Claude Code Swarm Orchestration

Master multi-agent orchestration using Claude Code's agent teams and task system.

Experimental: Agent teams are disabled by default. Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS in your settings.json or environment.


Primitives

PrimitiveWhat It IsFile Location
AgentA Claude instance that can use tools. You are an agent. Subagents are agents you spawn.N/A (process)
TeamA named group of agents working together. One leader, multiple teammates.~/.claude/teams/{name}/config.json
TeammateAn agent that joined a team. Has a name, color, inbox. Spawned via Task with team_name + name.Listed in team config
LeaderThe agent that created the team. Receives teammate messages, approves plans/shutdowns.First member in config
TaskA work item with subject, description, status, owner, and dependencies.~/.claude/tasks/{team}/N.json
InboxJSON file where an agent receives messages from teammates.~/.claude/teams/{name}/inboxes/{agent}.json
MessageA JSON object sent between agents. Can be text or structured (shutdown_request, idle_notification, etc).Stored in inbox files
BackendHow teammates run. Auto-detected: in-process (same Node.js, invisible), tmux (separate panes, visible), iterm2 (split panes in iTerm2). See Spawn Backends.Auto-detected based on environment

How They Connect

mermaid
flowchart TB
    subgraph TEAM[TEAM]
        Leader[Leader - you]
        T1[Teammate 1]
        T2[Teammate 2]

        Leader <-->|messages via inbox| T1
        Leader <-->|messages via inbox| T2
        T1 <-.->|can message| T2
    end

    subgraph TASKS[TASK LIST]
        Task1["#1 completed: Research<br/>owner: teammate1"]
        Task2["#2 in_progress: Implement<br/>owner: teammate2"]
        Task3["#3 pending: Test<br/>blocked by #2"]
    end

    T1 --> Task1
    T2 --> Task2
    Task2 -.->|unblocks| Task3

Lifecycle

mermaid
flowchart LR
    A[1. Create Team] --> B[2. Create Tasks]
    B --> C[3. Spawn Teammates]
    C --> D[4. Work]
    D --> E[5. Coordinate]
    E --> F[6. Shutdown]
    F --> G[7. Cleanup]

Message Flow

mermaid
sequenceDiagram
    participant L as Leader
    participant T1 as Teammate 1
    participant T2 as Teammate 2
    participant Tasks as Task List

    L->>Tasks: TaskCreate (3 tasks)
    L->>T1: spawn with prompt
    L->>T2: spawn with prompt

    T1->>Tasks: claim task #1
    T2->>Tasks: claim task #2

    T1->>Tasks: complete #1
    T1->>L: SendMessage (findings)

    Note over Tasks: #3 auto-unblocks

    T2->>Tasks: complete #2
    T2->>L: SendMessage (findings)

    L->>T1: SendMessage (shutdown_request)
    T1->>L: SendMessage (shutdown_response, approve)
    L->>T2: SendMessage (shutdown_request)
    T2->>L: SendMessage (shutdown_response, approve)

    L->>L: TeamDelete

Sub-Skills Index

SkillWhat It Covers
Team ManagementCreate teams, spawn teammates, delegate mode, permissions, shutdown, cleanup
Task SystemTaskCreate, TaskList, TaskGet, TaskUpdate, dependencies, file locking
Agent TypesBuilt-in agents (Bash, Explore, Plan, general-purpose), plugin agents, selection guide
MessagingSendMessage (all types), message formats, automatic delivery, direct interaction
Orchestration Patterns7 patterns (parallel, pipeline, swarm, research, plan approval, refactoring, RLM)
RLM PatternChunked analysis of large files using RLM (Recursive Language Model) pattern
Spawn Backendsin-process, tmux, iTerm2, teammateMode setting, auto-detection
Error HandlingCommon errors, hooks (TeammateIdle, TaskCompleted), limitations, debugging

Quick Reference

Create Team and Spawn Teammate

javascript
TeamCreate({ team_name: "my-team", description: "Working on feature X" })
Task({ team_name: "my-team", name: "worker", subagent_type: "general-purpose", prompt: "...", run_in_background: true })

Spawn Subagent (No Team)

javascript
Task({ subagent_type: "Explore", description: "Find files", prompt: "..." })

Message Teammate

javascript
SendMessage({ type: "message", recipient: "worker-1", content: "...", summary: "Brief update" })

Create Task Pipeline

javascript
TaskCreate({ subject: "Step 1", description: "...", activeForm: "Working on step 1..." })
TaskCreate({ subject: "Step 2", description: "...", activeForm: "Working on step 2..." })
TaskUpdate({ taskId: "2", addBlockedBy: ["1"] })

Shutdown Team

javascript
SendMessage({ type: "shutdown_request", recipient: "worker-1", content: "All done" })
// Wait for approval...
TeamDelete()

Based on Claude Code agent teams documentation - Updated 2026-02-07