AGENT SKILL

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 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

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 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.

Workflow: Plan → Dispatch → Monitor → Report

  1. Plan: Call plan_project(prompt="...") → returns project_id + list of missions with depends_on chains and auto_dispatch=true.
  2. Show plan: Present mission titles, types, and dependency chain to the user.
  3. 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).
  4. Monitor: Call get_mission_status(mission_id=...) or get_dashboard() to check progress.
  5. 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

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

Manual: step-by-step control

  1. create_project(name="My Project") → returns project_id.
  2. 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.
  3. dispatch_mission(mission_id=...) on the first mission to start the chain.
  4. get_report(mission_id=...) when done.

Sequential with review

  1. create_project(name="...") → get project_id.
  2. create_mission(project_id=project_id, title="Implement feature", prompt="...") → get impl_mission_id.
  3. dispatch_mission(mission_id=impl_mission_id), then poll with get_mission_status until complete.
  4. get_report(mission_id=impl_mission_id) to review results.
  5. 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=true if you want them to trigger automatically when dependencies complete. Without this flag, missions stay in draft status.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1