claude-devfleet

Orchestrates parallel Claude Code agents across isolated git worktrees via MCP.

Updated May 19, 2026
One-click install
npx skills add https://github.com/azusagasaku/--claude-config --skill claude-devfleet-azusagasaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-devfleet
Source: https://github.com/azusagasaku/--claude-config/tree/main/skills/ecc/claude-devfleet
Command: npx skills add https://github.com/azusagasaku/--claude-config --skill claude-devfleet-azusagasaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple coding agents on a single project manually is error-prone and slow. This Skill lets you plan a project, dispatch Claude Code agents to work in parallel within isolated git worktrees, monitor their progress, and read structured completion reports through a running Claude DevFleet MCP server. ## Core Features & Use Cases - AI Project Planning: Call plan_project to break a natural-language description into a project with chained missions and dependency DAGs. - Parallel Agent Dispatch: Launch agents with dispatch_mission, with automatic queuing and auto-dispatch of dependent missions as slots free up (default 3 concurrent agents). - Monitoring & Reporting: Track progress with get_mission_status and get_dashboard, then read structured reports via get_report covering files changed, errors, and next steps. - Use Case: Ask to build a REST API with auth and tests; the Skill plans the missions, dispatches the root mission, auto-dispatches dependents after auto-merge, and reports results back to you. ## Quick Start Connect the DevFleet MCP server and ask the assistant to plan and launch a project, for example: plan and build a REST API with authentication and tests using DevFleet.

Frequently Asked Questions about claude-devfleet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple Claude Code agents in parallel?▼

Use Claude DevFleet connected via MCP, then call plan_project to break a task into missions and dispatch_mission to start agents. Each agent runs in an isolated git worktree, with up to 3 concurrent agents by default.

How do I set up the Claude DevFleet MCP server?▼

Run claude mcp add devfleet --transport http http://localhost:18801/mcp to register the server. A running DevFleet instance must be reachable at that endpoint before any planning or dispatch tools work.

How do mission dependencies work in DevFleet?▼

Pass depends_on as a list of mission ID strings when calling create_mission, forming a DAG. Set auto_dispatch=true so a mission starts automatically once its dependencies complete; circular dependencies are not allowed.

What happens when a DevFleet agent hits a merge conflict?▼

Each agent works in an isolated git worktree and auto-merges on completion. If a merge conflict occurs, the changes stay on the agent's worktree branch so you can resolve the conflict manually.

Why is my DevFleet mission stuck in draft status?▼

Missions created without auto_dispatch=true remain in draft status and never start on their own. Either set auto_dispatch=true at creation or call dispatch_mission manually with the mission ID.

Should I use wait_for_mission or poll mission status?▼

wait_for_mission blocks the conversation for up to timeout_seconds (default 600), which hides progress from the user. For long-running missions, poll get_mission_status every 30-60 seconds instead.