[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2PAYJSFPTMCCFHR3W3FQ0":3,"skill-same:01M7C2PAYJSFPTMCCFHR3W3FQ0":45},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7C2PAYJSFPTMCCFHR3W3FQ0","subagent-dispatch-timing",null,"Use when deciding whether, when and how to dispatch subagents (including browser-use verification agents) during planning, implementation, verification and review in cg-work workflows; single source of dispatch judgement, not a state machine or evidence gate.","GFigting\u002Fcarry-god","GFigting","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38547422?v=4","01M7C26QXMKVWF4S758VG8TNAX","songgf","01M7C26QY80HTSAQRNF02D3PE6",0,"MIT","https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fsubagent-dispatch-timing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: subagent-dispatch-timing\ndescription: Use when deciding whether, when and how to dispatch subagents (including browser-use verification agents) during planning, implementation, verification and review in cg-work workflows; single source of dispatch judgement, not a state machine or evidence gate.\n---\n\n# 子智能体派发时机\n\n本技能是框架内子智能体派发判据的唯一来源：回答\"何时派发、何时不派发、各阶段如何派发\"。工作流与 core 只保留指向本技能的指针，不复制正文。本技能不改变任务状态机、证据门禁与交付路径规则。\n\n## 总则：比例原则\n\n默认最小交付。仅当派发子智能体带来以下三类明确增益之一时才派发：\n\n1. **上下文隔离**：任务只需局部上下文，或任务会产生大体量输出（长探索、大量命令结果），需要保护主会话上下文。\n2. **并行**：工作可拆分为边界互不重叠（按文件所有权切分）的独立部分。\n3. **独立视角**：需要不受实施者立场污染的审查或验收结论。\n\n无以上增益时不派发：单模块小刀改动、可直接验证的行为调整、主 Agent 亲自完成更快的场景，一律由主 Agent 直接执行。轻量执行档（`delivery_path: lightweight`）默认不派发任何子智能体。\n\n## 分阶段判据\n\n### 计划阶段\n\n- 跨模块、高风险或用户明确要求审查的任务：可并行派发两个子智能体做两线计划审核——**需求审核线**只判断需求覆盖、验收标准、范围遗漏或越界；**规范审核线**只判断计划结构、依赖、步骤、风险、验证可执行性和项目规范；均按\"问题—依据—建议\"输出。\n- 同一子智能体不应同时代表需求方和规范方作最终结论。\n- 轻量档与单模块小刀不做计划审核派发。\n\n### 实现阶段\n\n- 执行含多个独立任务的实现计划时，按镜像技能 `subagent-driven-development`（同会话）或 `executing-plans`（并行会话）的流程派发实现子代理；需要并行派发时按 `dispatching-parallel-agents` 执行，任务边界按文件所有权切分。本技能只引用这些镜像正文，不复制其流程。\n- 实现类子代理不并行派发（文件冲突）；审查类可并行。\n- 同形状小改动（同一类一行修改、常量替换、字段添加重复出现在多个文件）合并为一次派发交给同一个子代理，作为一个整体审查；只有需要独立判断、独立测试或独立审查面的工作才逐任务派发。\n- 实现子代理不得再派发子代理（既不派助手也不派审查者）；审查由派发它的控制方安排。\n- 单任务、单文件、主 Agent 可直接完成时不派发。\n\n### 验证阶段\n\n- Web 项目的页面与用户路径验收统一派发 browser-use 子代理：按项目上下文 `verification.profiles` 中配置的步骤执行，结果（截图、控制台日志、网络请求证据）回写任务 `verification.md`。\n- 项目无对应验证 profile 或无浏览器界面时，不派发 browser-use；不得以静态检查或口头声明冒充页面验收结论。\n- 验证记录必须区分已通过、环境受限未执行和不适用，不能以替代检查冒充完整检查。\n- 纯浏览器验收存在边界：不覆盖数据库字段校验与日志警告类问题，此类校验必须结合接口\u002F数据层检查才能兜住功能正确性。\n\n### 审查收尾阶段\n\n- 审查类子智能体可并行派发（如规范与需求两个视角分线审查）。\n- 子智能体意见由主 Agent 汇总、去重并决定是否采纳，最终结论写回任务记录（该责任是 core 不变量，见 [工作模型](..\u002F..\u002Fcore\u002Foperating-model.md#计划、审查与验证的边界)）。\n- 主 Agent 不代替子代理修复问题后跳过审查；涉及业务取舍的结论交由用户确认。\n- 轻量档自审即可，不强制派发审查子智能体。\n\n## 派发契约\n\n- 派发词只包含该任务自身所需内容：任务定位一句话、需求或简报文件路径、上游任务留下的接口与决定、歧义的处理结论、报告文件路径与回传契约。不粘贴会话历史与累积摘要。\n- 大体量交付物以文件路径交接，不把内容驻留进主上下文。\n- 派发时明确模型选择：按任务复杂度选择够用的最低档位，省略模型会静默继承会话默认模型。\n- 等待已派发的子代理时不轮询短超时、不做无限静默等待；有本地工作（更新记录、准备下一步交接）就继续做，真正空闲时分段有界等待并核对在派子代理状态。\n\n## 反模式\n\n以下偏差一经发现即纠正：\n\n- **该派不派**：Web 验收跳过 browser-use 派发，用静态检查、代码阅读或口头声明冒充页面验收结论。\n- **过度派发**：轻量任务派发子智能体；逐条审查发现各派一个修复代理（应合并为一次修复派发）；为同一差异重复派发多个审查席位；实现子代理自派审查者造成重复席位。\n- **错误并行**：并行派发多个实现子代理造成文件冲突；并行派发时未按文件所有权切分边界。\n\n## 边界\n\n- 本技能不复制镜像技能正文；多任务计划执行、并行派发、跨会话执行的流程细节分别以 `subagent-driven-development`、`dispatching-parallel-agents`、`executing-plans` 镜像为准。\n- 本技能不新增任务状态、产物文件或校验门禁；派发结论作为对应阶段证据写入既有任务记录。\n- 外部、破坏性、生产、认证、部署或跨会话操作的授权边界仍以 [特殊操作](..\u002F..\u002Fcore\u002Fspecial-operations.md) 为准，派发判据不替代授权要求。\n","# 子智能体派发时机\n\n本技能是框架内子智能体派发判据的唯一来源：回答\"何时派发、何时不派发、各阶段如何派发\"。工作流与 core 只保留指向本技能的指针，不复制正文。本技能不改变任务状态机、证据门禁与交付路径规则。\n\n## 总则：比例原则\n\n默认最小交付。仅当派发子智能体带来以下三类明确增益之一时才派发：\n\n1. **上下文隔离**：任务只需局部上下文，或任务会产生大体量输出（长探索、大量命令结果），需要保护主会话上下文。\n2. **并行**：工作可拆分为边界互不重叠（按文件所有权切分）的独立部分。\n3. **独立视角**：需要不受实施者立场污染的审查或验收结论。\n\n无以上增益时不派发：单模块小刀改动、可直接验证的行为调整、主 Agent 亲自完成更快的场景，一律由主 Agent 直接执行。轻量执行档（`delivery_path: lightweight`）默认不派发任何子智能体。\n\n## 分阶段判据\n\n### 计划阶段\n\n- 跨模块、高风险或用户明确要求审查的任务：可并行派发两个子智能体做两线计划审核——**需求审核线**只判断需求覆盖、验收标准、范围遗漏或越界；**规范审核线**只判断计划结构、依赖、步骤、风险、验证可执行性和项目规范；均按\"问题—依据—建议\"输出。\n- 同一子智能体不应同时代表需求方和规范方作最终结论。\n- 轻量档与单模块小刀不做计划审核派发。\n\n### 实现阶段\n\n- 执行含多个独立任务的实现计划时，按镜像技能 `subagent-driven-development`（同会话）或 `executing-plans`（并行会话）的流程派发实现子代理；需要并行派发时按 `dispatching-parallel-agents` 执行，任务边界按文件所有权切分。本技能只引用这些镜像正文，不复制其流程。\n- 实现类子代理不并行派发（文件冲突）；审查类可并行。\n- 同形状小改动（同一类一行修改、常量替换、字段添加重复出现在多个文件）合并为一次派发交给同一个子代理，作为一个整体审查；只有需要独立判断、独立测试或独立审查面的工作才逐任务派发。\n- 实现子代理不得再派发子代理（既不派助手也不派审查者）；审查由派发它的控制方安排。\n- 单任务、单文件、主 Agent 可直接完成时不派发。\n\n### 验证阶段\n\n- Web 项目的页面与用户路径验收统一派发 browser-use 子代理：按项目上下文 `verification.profiles` 中配置的步骤执行，结果（截图、控制台日志、网络请求证据）回写任务 `verification.md`。\n- 项目无对应验证 profile 或无浏览器界面时，不派发 browser-use；不得以静态检查或口头声明冒充页面验收结论。\n- 验证记录必须区分已通过、环境受限未执行和不适用，不能以替代检查冒充完整检查。\n- 纯浏览器验收存在边界：不覆盖数据库字段校验与日志警告类问题，此类校验必须结合接口\u002F数据层检查才能兜住功能正确性。\n\n### 审查收尾阶段\n\n- 审查类子智能体可并行派发（如规范与需求两个视角分线审查）。\n- 子智能体意见由主 Agent 汇总、去重并决定是否采纳，最终结论写回任务记录（该责任是 core 不变量，见 [工作模型](..\u002F..\u002Fcore\u002Foperating-model.md#计划、审查与验证的边界)）。\n- 主 Agent 不代替子代理修复问题后跳过审查；涉及业务取舍的结论交由用户确认。\n- 轻量档自审即可，不强制派发审查子智能体。\n\n## 派发契约\n\n- 派发词只包含该任务自身所需内容：任务定位一句话、需求或简报文件路径、上游任务留下的接口与决定、歧义的处理结论、报告文件路径与回传契约。不粘贴会话历史与累积摘要。\n- 大体量交付物以文件路径交接，不把内容驻留进主上下文。\n- 派发时明确模型选择：按任务复杂度选择够用的最低档位，省略模型会静默继承会话默认模型。\n- 等待已派发的子代理时不轮询短超时、不做无限静默等待；有本地工作（更新记录、准备下一步交接）就继续做，真正空闲时分段有界等待并核对在派子代理状态。\n\n## 反模式\n\n以下偏差一经发现即纠正：\n\n- **该派不派**：Web 验收跳过 browser-use 派发，用静态检查、代码阅读或口头声明冒充页面验收结论。\n- **过度派发**：轻量任务派发子智能体；逐条审查发现各派一个修复代理（应合并为一次修复派发）；为同一差异重复派发多个审查席位；实现子代理自派审查者造成重复席位。\n- **错误并行**：并行派发多个实现子代理造成文件冲突；并行派发时未按文件所有权切分边界。\n\n## 边界\n\n- 本技能不复制镜像技能正文；多任务计划执行、并行派发、跨会话执行的流程细节分别以 `subagent-driven-development`、`dispatching-parallel-agents`、`executing-plans` 镜像为准。\n- 本技能不新增任务状态、产物文件或校验门禁；派发结论作为对应阶段证据写入既有任务记录。\n- 外部、破坏性、生产、认证、部署或跨会话操作的授权边界仍以 [特殊操作](..\u002F..\u002Fcore\u002Fspecial-operations.md) 为准，派发判据不替代授权要求。\n",{"name":5,"description":7},"main","56a75152926303000e7816fcfed6219beb77d77c","cg-work\u002Fskills\u002Fsubagent-dispatch-timing","https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god","https:\u002F\u002Fgithub.com\u002FGFigting","hhhh man","2026-11-03 17:54:51",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GFigting\u002Fcarry-god --skill subagent-dispatch-timing",{"tool":37,"command":38},"bunx","bunx skills add GFigting\u002Fcarry-god --skill subagent-dispatch-timing",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GFigting\u002Fcarry-god --skill subagent-dispatch-timing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fsubagent-dispatch-timing\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7C2QJRTBFR5MSG60P9WK2SB","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7C2QFDSHKWY85TNNJXH8NVZ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7C2QBB4PJ80M5ZNNXGCBQ83","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7C2Q74FS7G59T5GMDE3XTVD","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\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"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":19},"01M7C2Q286D0F57CT6C4V2VK6M","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\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"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":87,"publishedAt":19},"01M7C2PYAN0AYG1498KNW6B6ES","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002FGFigting\u002Fcarry-god\u002Fblob\u002Fmain\u002Fcg-work\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[]]