跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 claude-devfleet

Claude Devfleet

管弦乐通过克洛德·德夫利特(Claude DevFleet)——计划项目,在孤立的工作树上派遣平行的代理,监测进度,并阅读结构化报告. 将并行编码代理发送到被隔离的工作树上并跟踪其报告时使用.

11033 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

通过克洛德·德弗利特(Claude DevFleet)执行多代理编码任务——规划项目,在孤立的工作树上派遣平行代理,监测进度并阅读结构化报告

何时用

当您需要发送多个 Claude 代码代理以并行进行编码任务时使用此技能. 每个特工都在一个孤立的活字树上运行 拥有完整的工具

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Claude DevFleet Multi-Agent Orchestration、When to Use、Setup、How It Works、Tools、Workflow: Plan → Dispatch → Monitor → Report。 其中含规范建议的小节:分步指令、输入输出示例。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports. Use when dispatching parallel coding agents across isolated worktrees and tracking their reports.

Claude DevFleet Multi-Agent OrchestrationWhen to UseSetupHow It WorksToolsWorkflow: Plan → Dispatch → Monitor → ReportConcurrencyExamplesFull auto: plan and launchManual: step-by-step controlSequential with reviewGuidelines

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
claude-devfleet
description
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports. Use when dispatching parallel coding agents across isolated worktrees and tracking their reports.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「claude-devfleet」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-72dd8d944f81a2a9-%E5%85%8B%E5%8A%B3%E5%BE%B7%C2%B7%E5%BE%B7%E5%A4%AB%E5%88%A9%E7%89%B9.html
请存为 .cursor/skills/claude-devfleet/SKILL.md 或 .claude/skills/claude-devfleet/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/affaan-m/ecc' --list

npx skills add 'https://github.com/affaan-m/ecc' --skill 'claude-devfleet'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: claude-devfleet description: Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports. Use when dispatching parallel coding agents across isolated worktrees and tracking their reports. metadata: origin: community --- # 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. ## Setup The DevFleet server is a separate project, not bundled with ECC. Install and run it from its repository first: Then connect the running instance via MCP: ```bash claude mcp add devfleet --transport http http://localhost:18801/mcp ``` Before first use, verify the process listening on port 18801 is the DevFleet binary you installed (see SECURITY.md on localhost MCP servers). ## 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=)` 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=[""])` 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.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…