claude-devfleet

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Claude DevFleet Multi-Agent Orchestration

Claude DevFleet多Agent编排

When to Use

使用场景

Use this skill when you need to dispatch multiple Claude Code agents to work on coding tasks in parallel. Each agent runs in an isolated git worktree with full tooling.

Requires a running Claude DevFleet instance connected via MCP:

bash

claude mcp add devfleet --transport http http://localhost:18801/mcp

当你需要调度多个Claude Code Agent并行处理编码任务时，可使用此技能。每个Agent都在独立的git worktree中运行，并配备完整工具链。

需要通过MCP连接运行中的Claude DevFleet实例：

bash

claude mcp add devfleet --transport http http://localhost:18801/mcp

How It Works

工作原理

User → "Build a REST API with auth and tests"
  ↓
plan_project(prompt) → project_id + mission DAG
  ↓
Show plan to user → get approval
  ↓
dispatch_mission(M1) → Agent 1 spawns in worktree
  ↓
M1 completes → auto-merge → auto-dispatch M2 (depends_on M1)
  ↓
M2 completes → auto-merge
  ↓
get_report(M2) → files_changed, what_done, errors, next_steps
  ↓
Report back to user

用户 → "构建带认证和测试的REST API"
  ↓
plan_project(prompt) → project_id + 任务DAG
  ↓
向用户展示规划 → 获取确认
  ↓
dispatch_mission(M1) → Agent 1在工作树中启动
  ↓
M1完成 → 自动合并 → 自动调度M2（依赖M1）
  ↓
M2完成 → 自动合并
  ↓
get_report(M2) → 文件变更、完成内容、错误信息、后续步骤
  ↓
向用户反馈报告

Tools

工具列表

Tool	Purpose
`plan_project(prompt)`	AI breaks a description into a project with chained missions
`create_project(name, path?, description?)`	Create a project manually, returns `project_id`
`create_mission(project_id, title, prompt, depends_on?, auto_dispatch?)`	Add a mission. `depends_on` is a list of mission ID strings (e.g., `["abc-123"]` ). Set `auto_dispatch=true` to auto-start when deps are met.
`dispatch_mission(mission_id, model?, max_turns?)`	Start an agent on a mission
`cancel_mission(mission_id)`	Stop a running agent
`wait_for_mission(mission_id, timeout_seconds?)`	Block until a mission completes (see note below)
`get_mission_status(mission_id)`	Check mission progress without blocking
`get_report(mission_id)`	Read structured report (files changed, tested, errors, next steps)
`get_dashboard()`	System overview: running agents, stats, recent activity
`list_projects()`	Browse all projects
`list_missions(project_id, status?)`	List missions in a project

Note on
wait_for_mission
: This blocks the conversation for up to
timeout_seconds
(default 600). For long-running missions, prefer polling with
get_mission_status
every 30–60 seconds instead, so the user sees progress updates.

工具	用途
`plan_project(prompt)`	AI将需求描述拆解为包含链式任务的项目
`create_project(name, path?, description?)`	手动创建项目，返回 `project_id`
`create_mission(project_id, title, prompt, depends_on?, auto_dispatch?)`	添加任务。 `depends_on` 为任务ID字符串列表（例如 `["abc-123"]` ）。设置 `auto_dispatch=true` 可在依赖满足时自动启动。
`dispatch_mission(mission_id, model?, max_turns?)`	启动Agent执行任务
`cancel_mission(mission_id)`	停止运行中的Agent
`wait_for_mission(mission_id, timeout_seconds?)`	阻塞直到任务完成（见下方说明）
`get_mission_status(mission_id)`	非阻塞式检查任务进度
`get_report(mission_id)`	查看结构化报告（文件变更、测试情况、错误信息、后续步骤）
`get_dashboard()`	系统概览：运行中的Agent、统计数据、近期活动
`list_projects()`	浏览所有项目
`list_missions(project_id, status?)`	列出项目中的任务

关于
wait_for_mission
的说明：此方法会阻塞对话，最长等待
timeout_seconds
秒（默认600秒）。对于长时间运行的任务，建议每隔30-60秒调用
get_mission_status
轮询，以便用户查看进度更新。

Workflow: Plan → Dispatch → Monitor → Report

工作流：规划 → 调度 → 监控 → 报告

Plan: Call

plan_project(prompt="...")

→ returns

project_id

+ list of missions with

depends_on

chains and

auto_dispatch=true

Show plan: Present mission titles, types, and dependency chain to the user.
Dispatch: Call
```
dispatch_mission(mission_id=<first_mission_id>)
```
on the root mission (empty
```
depends_on
```
). Remaining missions auto-dispatch as their dependencies complete (because
```
plan_project
```
sets
```
auto_dispatch=true
```
on them).

Monitor: Call

get_mission_status(mission_id=...)

get_dashboard()

to check progress.

Report: Call
```
get_report(mission_id=...)
```
when missions complete. Share highlights with the user.

规划：调用
```
plan_project(prompt="...")
```
→ 返回
```
project_id
```
以及包含
```
depends_on
```
依赖链和
```
auto_dispatch=true
```
设置的任务列表。
展示规划：向用户展示任务标题、类型和依赖链。
调度：对根任务（
```
depends_on
```
为空）调用
```
dispatch_mission(mission_id=<first_mission_id>)
```
。剩余任务会在依赖完成时自动调度（因为
```
plan_project
```
为它们设置了
```
auto_dispatch=true
```
）。

监控：调用

get_mission_status(mission_id=...)

或

get_dashboard()

检查进度。

报告：任务完成后调用
```
get_report(mission_id=...)
```
，并向用户分享重点内容。

Concurrency

并发处理

DevFleet runs up to 3 concurrent agents by default (configurable via

DEVFLEET_MAX_AGENTS

). When all slots are full, missions with

auto_dispatch=true

queue in the mission watcher and dispatch automatically as slots free up. Check

get_dashboard()

for current slot usage.

DevFleet默认最多运行3个并发Agent（可通过

DEVFLEET_MAX_AGENTS

配置）。当所有Agent槽位占满时，设置了

auto_dispatch=true

的任务会进入任务监控队列，待槽位释放后自动调度。可通过

get_dashboard()

查看当前槽位使用情况。

Examples

示例

Full auto: plan and launch

全自动：规划并启动

```
plan_project(prompt="...")
```
→ shows plan with missions and dependencies.
Dispatch the first mission (the one with empty
```
depends_on
```
).
Remaining missions auto-dispatch as dependencies resolve (they have
```
auto_dispatch=true
```
).
Report back with project ID and mission count so the user knows what was launched.
Poll with
```
get_mission_status
```
or
```
get_dashboard()
```
periodically until all missions reach a terminal state (
```
completed
```
,
```
failed
```
, or
```
cancelled
```
).
```
get_report(mission_id=...)
```
for each terminal mission — summarize successes and call out failures with errors and next steps.

```
plan_project(prompt="...")
```
→ 展示包含任务和依赖的规划。
调度第一个任务（
```
depends_on
```
为空的任务）。
剩余任务会在依赖满足时自动调度（它们已设置
```
auto_dispatch=true
```
）。
向用户反馈项目ID和任务数量，让用户了解已启动的任务。
定期调用
```
get_mission_status
```
或
```
get_dashboard()
```
轮询，直到所有任务进入终态（
```
completed
```
、
```
failed
```
或
```
cancelled
```
）。
对每个终态任务调用
```
get_report(mission_id=...)
```
—— 总结成功内容，并标注失败任务的错误信息和后续步骤。

Manual: step-by-step control

手动模式：分步控制

create_project(name="My Project")

→ returns

project_id

create_mission(project_id=project_id, title="...", prompt="...", auto_dispatch=true)

for the first (root) mission → capture

root_mission_id

create_mission(project_id=project_id, title="...", prompt="...", auto_dispatch=true, depends_on=["<root_mission_id>"])

for each subsequent task.

```
dispatch_mission(mission_id=...)
```
on the first mission to start the chain.
```
get_report(mission_id=...)
```
when done.

create_project(name="My Project")

→ 返回

project_id

。

为第一个（根）任务调用

create_mission(project_id=project_id, title="...", prompt="...", auto_dispatch=true)

→ 记录

root_mission_id

。为后续每个任务调用

create_mission(project_id=project_id, title="...", prompt="...", auto_dispatch=true, depends_on=["<root_mission_id>"])

。

对第一个任务调用
```
dispatch_mission(mission_id=...)
```
以启动任务链。
完成后调用
```
get_report(mission_id=...)
```
。

Sequential with review

带审核的串行模式

```
create_project(name="...")
```
→ get
```
project_id
```
.

create_mission(project_id=project_id, title="Implement feature", prompt="...")

→ get

impl_mission_id

dispatch_mission(mission_id=impl_mission_id)

, then poll with

get_mission_status

until complete.

```
get_report(mission_id=impl_mission_id)
```
to review results.

create_mission(project_id=project_id, title="Review", prompt="...", depends_on=[impl_mission_id], auto_dispatch=true)

— auto-starts since the dependency is already met.

```
create_project(name="...")
```
→ 获取
```
project_id
```
。

create_mission(project_id=project_id, title="实现功能", prompt="...")

→ 获取

impl_mission_id

。

调用

dispatch_mission(mission_id=impl_mission_id)

，然后通过

get_mission_status

轮询直到完成。

调用
```
get_report(mission_id=impl_mission_id)
```
审核结果。

create_mission(project_id=project_id, title="审核", prompt="...", depends_on=[impl_mission_id], auto_dispatch=true)

—— 由于依赖已满足，会自动启动。

Guidelines

—

Always confirm the plan with the user before dispatching, unless they said to go ahead.
Include mission titles and IDs when reporting status.
If a mission fails, read its report before retrying.
Check
```
get_dashboard()
```
for agent slot availability before bulk dispatching.
Mission dependencies form a DAG — do not create circular dependencies.
Each agent runs in an isolated git worktree and auto-merges on completion. If a merge conflict occurs, the changes remain on the agent's worktree branch for manual resolution.
When manually creating missions, always set
```
auto_dispatch=true
```
if you want them to trigger automatically when dependencies complete. Without this flag, missions stay in
```
draft
```
status.

—