[{"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,90,97,104,111],{"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},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":88,"publishedAt":89},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":89},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":89},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]