claude-devfleet
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- claude-devfleet
- origin
- community
- description
- Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
03 SKILL.md 正文
Claude DevFleet Multi-Agent Orchestration
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:
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
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 totimeout_seconds(default 600). For long-running missions, prefer polling withget_mission_statusevery 30–60 seconds instead, so the user sees progress updates.
Workflow: Plan → Dispatch → Monitor → Report
- Plan: Call
plan_project(prompt="...")→ returnsproject_id+ list of missions withdepends_onchains andauto_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 (emptydepends_on). Remaining missions auto-dispatch as their dependencies complete (becauseplan_projectsetsauto_dispatch=trueon them). - Monitor: Call
get_mission_status(mission_id=...)orget_dashboard()to check progress. - Report: Call
get_report(mission_id=...)when missions complete. Share highlights with the user.
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.
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_statusorget_dashboard()periodically until all missions reach a terminal state (completed,failed, orcancelled). get_report(mission_id=...)for each terminal mission — summarize successes and call out failures with errors and next steps.
Manual: step-by-step control
create_project(name="My Project")→ returnsproject_id.create_mission(project_id=project_id, title="...", prompt="...", auto_dispatch=true)for the first (root) mission → captureroot_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.
Sequential with review
create_project(name="...")→ getproject_id.create_mission(project_id=project_id, title="Implement feature", prompt="...")→ getimpl_mission_id.dispatch_mission(mission_id=impl_mission_id), then poll withget_mission_statusuntil 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.
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=trueif you want them to trigger automatically when dependencies complete. Without this flag, missions stay indraftstatus.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.