Claude Devfleet
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of claude-devfleet by affaan-m - installs and ranking accrue to the original listing.
Claude DevFleet is a Claude Code skill that orchestrates parallel coding agents in isolated git worktrees via MCP for developers who need multi-mission implementation with automated merges and reporting.
About
Claude DevFleet is a multi-agent orchestration skill for Claude Code that connects to a running DevFleet MCP server at http://localhost:18801/mcp. Developers register the server with `claude mcp add devfleet --transport http http://localhost:18801/mcp`, then call plan_project to turn a prompt into a mission DAG, approve the plan, and dispatch missions so each agent works in its own git worktree with full tool access. Completed missions auto-merge before dependent missions dispatch, and get_report returns files_changed and structured completion data. Reach for Claude DevFleet when a single agent cannot safely parallelize backend, auth, tests, or refactors across branches.
- Breaks user prompts into a mission DAG via plan_project tool
- Dispatches parallel Claude agents into isolated git worktrees
- Automatic dependency handling with sequential auto-merge and dispatch
- Structured progress reports with files_changed, errors, and next_steps
- Requires separate DevFleet MCP server running on localhost:18801
Claude Devfleet by the numbers
- 1,389 all-time installs (skills.sh)
- +84 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill claude-devfleetAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you run parallel Claude agents in git worktrees?
Orchestrate multiple Claude agents working in parallel on complex coding projects using isolated git worktrees.
Who is it for?
Developers running Claude Code with DevFleet who need approved multi-mission plans executed in parallel isolated worktrees.
Skip if: Developers without a running Claude DevFleet MCP instance or single-file edits that do not benefit from parallel agent dispatch.
When should I use this skill?
User asks to parallelize Claude agents, dispatch missions, or orchestrate multi-step coding across git worktrees with DevFleet.
What you get
Mission DAG plan, per-mission agent worktrees, auto-merged branches, and structured get_report output with files_changed.
- Mission DAG plan
- Per-mission worktree branches
- Structured mission reports
By the numbers
- DevFleet MCP endpoint listens on localhost port 18801
- Workflow chains plan_project, dispatch_mission, auto-merge, and get_report
Files
Claude DevFleet マルチエージェント オーケストレーション
使用時期
このスキルは、複数のClaude Codeエージェントをコーディングタスクで並行して作業するように派遣する必要があるときに使用します。各エージェントは完全なツール機能を備えた分離されたgit作業ツリーで実行されます。
実行中のClaude DevFleetインスタンスが必要で、MCP経由で接続：
claude mcp add devfleet --transport http http://localhost:18801/mcp動作方法
User → 「認証とテスト付きのREST APIを構築」
↓
plan_project(prompt) → project_id + mission DAG
↓
計画をユーザーに表示 → 承認を取得
↓
dispatch_mission(M1) → エージェント1は作業ツリーで生成
↓
M1完了 → 自動マージ → M2を自動派遣（M1に依存）
↓
M2完了 → 自動マージ
↓
get_report(M2) → files_changed、what_done、errors、next_steps
↓
ユーザーに報告するツール
| Tool | Purpose |
|---|---|
plan_project(prompt) | AIが説明をミッションチェーン付きプロジェクトに分割 |
create_project(name, path?, description?) | プロジェクトを手動で作成、project_idを返す |
create_mission(project_id, title, prompt, depends_on?, auto_dispatch?) | ミッションを追加。depends_onはミッションIDの文字列のリスト。auto_dispatch=trueで依存関係が満たされたとき自動開始。 |
dispatch_mission(mission_id, model?, max_turns?) | ミッション上でエージェントを開始 |
cancel_mission(mission_id) | 実行中のエージェントを停止 |
wait_for_mission(mission_id, timeout_seconds?) | ミッション完了までブロック |
get_mission_status(mission_id) | ブロックなしでミッション進捗をチェック |
get_report(mission_id) | 構造化レポートを読む |
get_dashboard() | システム概要：実行中のエージェント、統計 |
list_projects() | すべてのプロジェクトをブラウザ |
list_missions(project_id, status?) | プロジェクト内のミッションをリスト |
ワークフロー
1. 計画：plan_project(prompt="...")を呼び出す → project_id + ミッションリスト 2. 表示：ユーザーにミッション計画を表示 3. 派遣：最初のミッションでdispatch_mission()を呼び出す 4. 監視：get_mission_status()で進捗をチェック 5. 報告：get_report()で完了時の報告
例
フル自動：計画と起動
1. plan_project(prompt="...") 2. 最初のミッションをDispatch 3. 残りのミッションは依存関係に基づいて自動Dispatch 4. 完了したらユーザーに報告
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Choose Claude DevFleet when missions need parallel isolated worktrees and automated merge sequencing instead of one sequential Claude Code session.
FAQ
What does Claude DevFleet require before dispatching agents?
Claude DevFleet requires a running Claude DevFleet instance and an MCP connection registered with `claude mcp add devfleet --transport http http://localhost:18801/mcp` before plan_project or dispatch_mission can run.
How does Claude DevFleet handle dependent coding missions?
Claude DevFleet completes each mission in an isolated git worktree, auto-merges the result, then automatically dispatches the next mission that depends on the finished work in the DAG.