[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70H9MCDSCV1RFSEG3JTJB0N":3,"skill-same:01M70H9MCDSCV1RFSEG3JTJB0N":73},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70H9MCDSCV1RFSEG3JTJB0N","team-agent-orchestration",null,"Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktrees — multi-agent fan-out, agent Kanban, squad coordination, or merging agent output into one product.","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\u002Fteam-agent-orchestration\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],"team agent orchestration","team","orchestration","agent orchestration","branch","when","scope","isolation","across","branches","kanban","worktrees","work","parallel","multi-agent","coordination","product","run","squad","merge","2026-11-10 10:12:30",false,"---\nname: team-agent-orchestration\ndescription: \"Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktrees — multi-agent fan-out, agent Kanban, squad coordination, or merging agent output into one product.\"\nmetadata:\n  origin: ECC\n---\n\n# Team Agent Orchestration\n\nUse this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.\n\n## When To Activate\n\n- The task spans multiple agents, tools, harnesses, branches, or worktrees.\n- The user mentions team orchestration, agent Kanban, squad, conductor, control pane, manager, desktop app, Zellij, tmux, Hermes, Devin, Codex, Claude Code, or multi-agent work.\n- A project needs shared workflow state across people and agents.\n- Existing agent fan-out is producing output but not mergeable product.\n\n## Operating Model\n\nTreat every agent as a teammate with a narrow contract:\n\n- **Owner**: the person or agent accountable for the work item.\n- **Scope**: files, branch, tool surface, and forbidden areas.\n- **State**: backlog, ready, running, review, blocked, merged, or archived.\n- **Evidence**: tests, screenshots, logs, review notes, or eval reports.\n- **Merge gate**: the exact condition that allows integration.\n\n## Agent Kanban\n\nUse agent Kanban when work must be visible across sessions.\n\n| Column | Meaning | Exit Criteria |\n| --- | --- | --- |\n| Backlog | Candidate work item, not yet shaped | Acceptance criteria written |\n| Ready | Shaped and assignable | Owner and branch\u002Fworktree assigned |\n| Running | Agent is actively working | Handoff artifact and changed files exist |\n| Review | Work is complete but not merged | Tests, diff review, and risk check pass |\n| Blocked | Needs external input or failed gate | Blocker has owner and next action |\n| Merged | Integrated into mainline | PR merged or local main updated |\n| Archived | No longer relevant | Reason recorded |\n\nEach card should fit this schema:\n\n```json\n{\n  \"id\": \"agent-card-001\",\n  \"title\": \"Build dynamic workflow skill\",\n  \"owner\": \"codex\",\n  \"state\": \"running\",\n  \"branch\": \"product\u002Fdynamic-workflow-team-orchestration\",\n  \"worktree\": \".\",\n  \"acceptance\": [\n    \"Skill exists\",\n    \"Tests cover required concepts\",\n    \"Content artifact contains video and article angles\"\n  ],\n  \"merge_gate\": \"lint, focused tests, and catalog check pass\",\n  \"handoff\": \"path\u002Fto\u002Fhandoff.md\"\n}\n```\n\n## Team-Based Orchestration Flow\n\n1. **Shape the board**: convert fuzzy ambition into work items with owners and merge gates.\n2. **Pick execution mode**: single-agent, dynamic workflow mode, dmux\u002Ftmux, worktree fan-out, or external desktop orchestrator.\n3. **Assign boundaries**: one owner per card, clear file scope, and no overlapping writes without an integrator.\n4. **Run agents**: each agent writes evidence and handoff notes, not just code.\n5. **Review in sequence**: tests first, then diff review, then security\u002Frisk checks, then content\u002Fproduct polish.\n6. **Merge deliberately**: one integrator resolves conflicts and updates the control pane or status artifact.\n7. **Extract reusable skill**: if the card pattern repeats, promote it into `skills\u002F`.\n\n## Control Pane Requirements\n\nA useful control pane for team orchestration should show:\n\n- Active work items and their agent Kanban state.\n- Owner, harness, branch, worktree, and last heartbeat.\n- Links to handoff artifacts, tests, screenshots, and PRs.\n- Blockers grouped by owner and unblock action.\n- Merge readiness by gate, not vibes.\n- Reusable workflow candidates that should become shared skills.\n\nDo not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?\n\n## Dynamic Workflow Compatibility\n\nWhen a card needs dynamic workflow mode:\n\n- Put the task-local harness under the card owner.\n- Store inputs and outputs on the card.\n- Require an eval before moving from Running to Review.\n- Promote the harness to a shared skill only after repeat use.\n\n## Failure Modes To Watch\n\n- **Agent soup**: many agents running, no owner or merge gate.\n- **Invisible work**: useful output exists only in a chat transcript.\n- **Board theater**: a Kanban board exists but cards have no acceptance criteria.\n- **Overlapping writes**: parallel agents edit the same files without worktrees.\n- **No product artifact**: the process produces docs but no runnable or publishable surface.\n\n## Output Standard\n\nFinish each orchestration pass with:\n\n- Board\u002Fcard changes.\n- Merged or pending branches.\n- Tests and eval evidence.\n- Blockers with owner and next action.\n- New shared skill candidates.\n","# Team Agent Orchestration\n\nUse this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.\n\n## When To Activate\n\n- The task spans multiple agents, tools, harnesses, branches, or worktrees.\n- The user mentions team orchestration, agent Kanban, squad, conductor, control pane, manager, desktop app, Zellij, tmux, Hermes, Devin, Codex, Claude Code, or multi-agent work.\n- A project needs shared workflow state across people and agents.\n- Existing agent fan-out is producing output but not mergeable product.\n\n## Operating Model\n\nTreat every agent as a teammate with a narrow contract:\n\n- **Owner**: the person or agent accountable for the work item.\n- **Scope**: files, branch, tool surface, and forbidden areas.\n- **State**: backlog, ready, running, review, blocked, merged, or archived.\n- **Evidence**: tests, screenshots, logs, review notes, or eval reports.\n- **Merge gate**: the exact condition that allows integration.\n\n## Agent Kanban\n\nUse agent Kanban when work must be visible across sessions.\n\n| Column | Meaning | Exit Criteria |\n| --- | --- | --- |\n| Backlog | Candidate work item, not yet shaped | Acceptance criteria written |\n| Ready | Shaped and assignable | Owner and branch\u002Fworktree assigned |\n| Running | Agent is actively working | Handoff artifact and changed files exist |\n| Review | Work is complete but not merged | Tests, diff review, and risk check pass |\n| Blocked | Needs external input or failed gate | Blocker has owner and next action |\n| Merged | Integrated into mainline | PR merged or local main updated |\n| Archived | No longer relevant | Reason recorded |\n\nEach card should fit this schema:\n\n```json\n{\n  \"id\": \"agent-card-001\",\n  \"title\": \"Build dynamic workflow skill\",\n  \"owner\": \"codex\",\n  \"state\": \"running\",\n  \"branch\": \"product\u002Fdynamic-workflow-team-orchestration\",\n  \"worktree\": \".\",\n  \"acceptance\": [\n    \"Skill exists\",\n    \"Tests cover required concepts\",\n    \"Content artifact contains video and article angles\"\n  ],\n  \"merge_gate\": \"lint, focused tests, and catalog check pass\",\n  \"handoff\": \"path\u002Fto\u002Fhandoff.md\"\n}\n```\n\n## Team-Based Orchestration Flow\n\n1. **Shape the board**: convert fuzzy ambition into work items with owners and merge gates.\n2. **Pick execution mode**: single-agent, dynamic workflow mode, dmux\u002Ftmux, worktree fan-out, or external desktop orchestrator.\n3. **Assign boundaries**: one owner per card, clear file scope, and no overlapping writes without an integrator.\n4. **Run agents**: each agent writes evidence and handoff notes, not just code.\n5. **Review in sequence**: tests first, then diff review, then security\u002Frisk checks, then content\u002Fproduct polish.\n6. **Merge deliberately**: one integrator resolves conflicts and updates the control pane or status artifact.\n7. **Extract reusable skill**: if the card pattern repeats, promote it into `skills\u002F`.\n\n## Control Pane Requirements\n\nA useful control pane for team orchestration should show:\n\n- Active work items and their agent Kanban state.\n- Owner, harness, branch, worktree, and last heartbeat.\n- Links to handoff artifacts, tests, screenshots, and PRs.\n- Blockers grouped by owner and unblock action.\n- Merge readiness by gate, not vibes.\n- Reusable workflow candidates that should become shared skills.\n\nDo not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?\n\n## Dynamic Workflow Compatibility\n\nWhen a card needs dynamic workflow mode:\n\n- Put the task-local harness under the card owner.\n- Store inputs and outputs on the card.\n- Require an eval before moving from Running to Review.\n- Promote the harness to a shared skill only after repeat use.\n\n## Failure Modes To Watch\n\n- **Agent soup**: many agents running, no owner or merge gate.\n- **Invisible work**: useful output exists only in a chat transcript.\n- **Board theater**: a Kanban board exists but cards have no acceptance criteria.\n- **Overlapping writes**: parallel agents edit the same files without worktrees.\n- **No product artifact**: the process produces docs but no runnable or publishable surface.\n\n## Output Standard\n\nFinish each orchestration pass with:\n\n- Board\u002Fcard changes.\n- Merged or pending branches.\n- Tests and eval evidence.\n- Blockers with owner and next action.\n- New shared skill candidates.\n",{"name":5,"metadata":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fteam-agent-orchestration",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 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill team-agent-orchestration",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill team-agent-orchestration",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill team-agent-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fteam-agent-orchestration\u002FSKILL.md",true,[],[74,82,108,130,149,164],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":100,"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",[88,91,96,97],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[101,102,103,104,105,106,107,29,36],"writing","writing skills","editing","deployment","use","Existing","new",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"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",[114,115,116],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},{"categoryNo":117,"categoryName":118,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000030","开发工程师",[101,120,121,122,29,123,124,105,125,126,127,128,129],"writing plans","plans","you","code","for","requirements","task","multi","spec","multi-step task",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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",[],[137,138,139,140,141,142,105,143,144,145,29,146,36,147,148],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"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",[155],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,105,29,161,162,163],"using superpowers","superpowers","conversation","how to","how","find","questions",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"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",[],[171,172,173,35,174,175,29,36,176,177,178,179,31,180,181,121,105,182,183],"using git worktrees","Using git","git","git worktrees","implementation","git worktree","worktree","native","Tools","fallback","feature","via","workspace"]