[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FPAKAV9VT8C9G3AXYERQJ":3,"skill-same:01M70FPAKAV9VT8C9G3AXYERQJ":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M70FPAKAV9VT8C9G3AXYERQJ","claude-devfleet",null,"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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fclaude-devfleet\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"claude devfleet","use","when","multi","via","progress","across","community","worktrees","reports","monitor","read","parallel","coding","multi-agent","projects","plan","parallel agents","orchestrate","tasks","2026-11-10 10:12:30",false,"---\nname: claude-devfleet\ndescription: 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.\nmetadata:\n  origin: community\n---\n\n# Claude DevFleet Multi-Agent Orchestration\n\n## When to Use\n\nUse 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.\n\n## Setup\n\nThe DevFleet server is a separate project, not bundled with ECC. Install and\nrun it from its repository first: \u003Chttps:\u002F\u002Fgithub.com\u002FLEC-AI\u002Fclaude-devfleet>\n\nThen connect the running instance via MCP:\n```bash\nclaude mcp add devfleet --transport http http:\u002F\u002Flocalhost:18801\u002Fmcp\n```\n\nBefore first use, verify the process listening on port 18801 is the DevFleet\nbinary you installed (see SECURITY.md on localhost MCP servers).\n\n## How It Works\n\n```\nUser → \"Build a REST API with auth and tests\"\n  ↓\nplan_project(prompt) → project_id + mission DAG\n  ↓\nShow plan to user → get approval\n  ↓\ndispatch_mission(M1) → Agent 1 spawns in worktree\n  ↓\nM1 completes → auto-merge → auto-dispatch M2 (depends_on M1)\n  ↓\nM2 completes → auto-merge\n  ↓\nget_report(M2) → files_changed, what_done, errors, next_steps\n  ↓\nReport back to user\n```\n\n### Tools\n\n| Tool | Purpose |\n|------|---------|\n| `plan_project(prompt)` | AI breaks a description into a project with chained missions |\n| `create_project(name, path?, description?)` | Create a project manually, returns `project_id` |\n| `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. |\n| `dispatch_mission(mission_id, model?, max_turns?)` | Start an agent on a mission |\n| `cancel_mission(mission_id)` | Stop a running agent |\n| `wait_for_mission(mission_id, timeout_seconds?)` | Block until a mission completes (see note below) |\n| `get_mission_status(mission_id)` | Check mission progress without blocking |\n| `get_report(mission_id)` | Read structured report (files changed, tested, errors, next steps) |\n| `get_dashboard()` | System overview: running agents, stats, recent activity |\n| `list_projects()` | Browse all projects |\n| `list_missions(project_id, status?)` | List missions in a project |\n\n> **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.\n\n### Workflow: Plan → Dispatch → Monitor → Report\n\n1. **Plan**: Call `plan_project(prompt=\"...\")` → returns `project_id` + list of missions with `depends_on` chains and `auto_dispatch=true`.\n2. **Show plan**: Present mission titles, types, and dependency chain to the user.\n3. **Dispatch**: Call `dispatch_mission(mission_id=\u003Cfirst_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).\n4. **Monitor**: Call `get_mission_status(mission_id=...)` or `get_dashboard()` to check progress.\n5. **Report**: Call `get_report(mission_id=...)` when missions complete. Share highlights with the user.\n\n### Concurrency\n\nDevFleet 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.\n\n## Examples\n\n### Full auto: plan and launch\n\n1. `plan_project(prompt=\"...\")` → shows plan with missions and dependencies.\n2. Dispatch the first mission (the one with empty `depends_on`).\n3. Remaining missions auto-dispatch as dependencies resolve (they have `auto_dispatch=true`).\n4. Report back with project ID and mission count so the user knows what was launched.\n5. Poll with `get_mission_status` or `get_dashboard()` periodically until all missions reach a terminal state (`completed`, `failed`, or `cancelled`).\n6. `get_report(mission_id=...)` for each terminal mission — summarize successes and call out failures with errors and next steps.\n\n### Manual: step-by-step control\n\n1. `create_project(name=\"My Project\")` → returns `project_id`.\n2. `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true)` for the first (root) mission → capture `root_mission_id`.\n   `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true, depends_on=[\"\u003Croot_mission_id>\"])` for each subsequent task.\n3. `dispatch_mission(mission_id=...)` on the first mission to start the chain.\n4. `get_report(mission_id=...)` when done.\n\n### Sequential with review\n\n1. `create_project(name=\"...\")` → get `project_id`.\n2. `create_mission(project_id=project_id, title=\"Implement feature\", prompt=\"...\")` → get `impl_mission_id`.\n3. `dispatch_mission(mission_id=impl_mission_id)`, then poll with `get_mission_status` until complete.\n4. `get_report(mission_id=impl_mission_id)` to review results.\n5. `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.\n\n## Guidelines\n\n- Always confirm the plan with the user before dispatching, unless they said to go ahead.\n- Include mission titles and IDs when reporting status.\n- If a mission fails, read its report before retrying.\n- Check `get_dashboard()` for agent slot availability before bulk dispatching.\n- Mission dependencies form a DAG — do not create circular dependencies.\n- 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.\n- 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.\n","# Claude DevFleet Multi-Agent Orchestration\n\n## When to Use\n\nUse 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.\n\n## Setup\n\nThe DevFleet server is a separate project, not bundled with ECC. Install and\nrun it from its repository first: \u003Chttps:\u002F\u002Fgithub.com\u002FLEC-AI\u002Fclaude-devfleet>\n\nThen connect the running instance via MCP:\n```bash\nclaude mcp add devfleet --transport http http:\u002F\u002Flocalhost:18801\u002Fmcp\n```\n\nBefore first use, verify the process listening on port 18801 is the DevFleet\nbinary you installed (see SECURITY.md on localhost MCP servers).\n\n## How It Works\n\n```\nUser → \"Build a REST API with auth and tests\"\n  ↓\nplan_project(prompt) → project_id + mission DAG\n  ↓\nShow plan to user → get approval\n  ↓\ndispatch_mission(M1) → Agent 1 spawns in worktree\n  ↓\nM1 completes → auto-merge → auto-dispatch M2 (depends_on M1)\n  ↓\nM2 completes → auto-merge\n  ↓\nget_report(M2) → files_changed, what_done, errors, next_steps\n  ↓\nReport back to user\n```\n\n### Tools\n\n| Tool | Purpose |\n|------|---------|\n| `plan_project(prompt)` | AI breaks a description into a project with chained missions |\n| `create_project(name, path?, description?)` | Create a project manually, returns `project_id` |\n| `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. |\n| `dispatch_mission(mission_id, model?, max_turns?)` | Start an agent on a mission |\n| `cancel_mission(mission_id)` | Stop a running agent |\n| `wait_for_mission(mission_id, timeout_seconds?)` | Block until a mission completes (see note below) |\n| `get_mission_status(mission_id)` | Check mission progress without blocking |\n| `get_report(mission_id)` | Read structured report (files changed, tested, errors, next steps) |\n| `get_dashboard()` | System overview: running agents, stats, recent activity |\n| `list_projects()` | Browse all projects |\n| `list_missions(project_id, status?)` | List missions in a project |\n\n> **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.\n\n### Workflow: Plan → Dispatch → Monitor → Report\n\n1. **Plan**: Call `plan_project(prompt=\"...\")` → returns `project_id` + list of missions with `depends_on` chains and `auto_dispatch=true`.\n2. **Show plan**: Present mission titles, types, and dependency chain to the user.\n3. **Dispatch**: Call `dispatch_mission(mission_id=\u003Cfirst_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).\n4. **Monitor**: Call `get_mission_status(mission_id=...)` or `get_dashboard()` to check progress.\n5. **Report**: Call `get_report(mission_id=...)` when missions complete. Share highlights with the user.\n\n### Concurrency\n\nDevFleet 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.\n\n## Examples\n\n### Full auto: plan and launch\n\n1. `plan_project(prompt=\"...\")` → shows plan with missions and dependencies.\n2. Dispatch the first mission (the one with empty `depends_on`).\n3. Remaining missions auto-dispatch as dependencies resolve (they have `auto_dispatch=true`).\n4. Report back with project ID and mission count so the user knows what was launched.\n5. Poll with `get_mission_status` or `get_dashboard()` periodically until all missions reach a terminal state (`completed`, `failed`, or `cancelled`).\n6. `get_report(mission_id=...)` for each terminal mission — summarize successes and call out failures with errors and next steps.\n\n### Manual: step-by-step control\n\n1. `create_project(name=\"My Project\")` → returns `project_id`.\n2. `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true)` for the first (root) mission → capture `root_mission_id`.\n   `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true, depends_on=[\"\u003Croot_mission_id>\"])` for each subsequent task.\n3. `dispatch_mission(mission_id=...)` on the first mission to start the chain.\n4. `get_report(mission_id=...)` when done.\n\n### Sequential with review\n\n1. `create_project(name=\"...\")` → get `project_id`.\n2. `create_mission(project_id=project_id, title=\"Implement feature\", prompt=\"...\")` → get `impl_mission_id`.\n3. `dispatch_mission(mission_id=impl_mission_id)`, then poll with `get_mission_status` until complete.\n4. `get_report(mission_id=impl_mission_id)` to review results.\n5. `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.\n\n## Guidelines\n\n- Always confirm the plan with the user before dispatching, unless they said to go ahead.\n- Include mission titles and IDs when reporting status.\n- If a mission fails, read its report before retrying.\n- Check `get_dashboard()` for agent slot availability before bulk dispatching.\n- Mission dependencies form a DAG — do not create circular dependencies.\n- 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.\n- 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.\n",{"name":5,"metadata":49,"description":7},{"origin":31},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fclaude-devfleet",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 06:54:12",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill claude-devfleet",{"tool":64,"command":65},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill claude-devfleet",{"tool":67,"command":68},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill claude-devfleet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fclaude-devfleet\u002FSKILL.md",true,[],[73,81,107,128,147,162],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M72JT3YP1SQHD0MANGDXQ4RT","higgsfield-websites","Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1\u002FR2\u002FKV\u002FDO\u002FContainers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references\u002Fwebsite-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references\u002Fapp-flow.md), `game` (realtime multiplayer rooms — references\u002Fgame-flow.md). Routes to the right flow; each carries its own rules and deploy\u002Fpublish gates.\nUse when: \"build me a website\", \"make a landing page\", \"create a web app\", \"build a SaaS dashboard \u002F portfolio\", \"make me a game\", \"deploy this site\", \"publish\". Also owns GAME ART: \"make a spritesheet\", \"tileable texture\", \"animate a 3D character\", game music\u002FSFX — see the game-* references.\nNOT for: single image\u002Fvideo\u002Faudio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fhiggsfield-ai_skills\u002Fhiggsfield-websites\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":99,"publishedAt":44},"01M70JPK8HAXXA85P7Q8NKZZYG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-skills\u002FSKILL.md",[87,90,95,96],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[100,101,102,103,25,104,105,26,106],"writing","writing skills","editing","deployment","Existing","new","work",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"publishedAt":44},"01M70JP4PHBH1CQVVDWZ94W159","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-plans\u002FSKILL.md",[113,114,115],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":116,"categoryName":117,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000030","开发工程师",[100,119,120,121,26,122,123,25,124,125,27,126,127],"writing plans","plans","you","code","for","requirements","task","spec","multi-step task",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":44},"01M70JNTYVGXFZT8PASZ844TH8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fverification-before-completion\u002FSKILL.md",[],[135,136,137,138,139,140,25,141,142,143,26,144,106,145,146],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":44},"01M70JNGVSQDESWN0Q5BPJ875V","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-superpowers\u002FSKILL.md",[153],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[155,156,157,158,25,26,159,160,161],"using superpowers","superpowers","conversation","how to","how","find","questions",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":44},"01M70JN57CE588NPYPYTWH1DWG","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[169,170,171,32,172,173,26,106,174,175,176,177,178,179,180,120,25,28,181],"using git worktrees","Using git","git","git worktrees","implementation","git worktree","worktree","native","Tools","isolation","fallback","feature","workspace"]