claude-devfleet

Coordinate parallel coding agents across mission DAGs in isolated git worktrees.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines launching, coordinating, and reporting on multiple coding agents working in parallel so teams can decompose projects into missions, run them concurrently in isolated worktrees, and collect structured results without manual orchestration.

Core Features & Use Cases

  • Plan and decompose: Break a high-level project prompt into a project and chained missions with dependency DAGs.
  • Dispatch and monitor: Start agents per mission, observe progress with non-blocking status checks or polling, and manage concurrency/queueing.
  • Auto-merge and reporting: Agents run in isolated git worktrees, auto-merge on success, and produce structured reports of files changed, tests, errors, and next steps.
  • Use Case: Split a new REST API implementation into feature, tests, and CI missions, dispatch the root mission, monitor progress, and collect per-mission reports for review.

Quick Start

Plan a project from a short prompt like "Build a REST API with auth and tests" and dispatch the root mission to launch parallel agents and return mission IDs.

Frequently Asked Questions about claude-devfleet

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

FAQPage Schema
How do I coordinate parallel coding agents for multi-mission software projects?

Coordinate parallel coding agents by decomposing projects into mission DAGs and dispatching them to isolated git worktrees. This enables dependency-aware dispatch, concurrent agent slot management, and auto-merge upon mission success.

What is the best way to run multiple coding agents concurrently in isolated git worktrees?

Running multiple coding agents concurrently requires dispatching missions to isolated git worktrees with auto-merge support. Agents operate independently, and you collect structured reports of files changed, tests, and errors without manual orchestration.

Can I decompose a high-level project prompt into chained missions with dependency DAGs?

Yes, you can plan and decompose a high-level project prompt into a project with chained missions using dependency DAGs. This structures complex implementations like REST APIs into feature, tests, and CI missions before dispatch.

Do I need a running Claude DevFleet instance connected via MCP to use this orchestration?

Yes, parallel agent orchestration requires a running Claude DevFleet instance connected via MCP. The APIs must expose plan_project, dispatch_mission, get_mission_status, and get_report with support for auto_dispatch and worktree isolation.

How do I monitor progress of dispatched coding agents without blocking my workflow?

Monitor dispatched coding agents using non-blocking status checks or polling via get_mission_status. This manages concurrency and queueing while returning mission IDs for tracking progress until structured reports are generated.