菜单
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.
Use when the user requests delegated implementation or multiple substantial tasks are genuinely independent without shared state. Do NOT use for coupled or ordinary single-task work.
| name | dispatching-parallel-agents |
| version | 6.2.0 |
| category | workflow |
| description | Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work. |
Parallelism is useful only when coordination costs and merge risk stay below the time saved.
Dispatch only when:
Do not delegate tiny tasks, related failures, exploratory debugging, or work that depends on sequential discoveries.
Run a full suite only if combined work changed shared core behavior, crosses a release boundary, or the user requested it.
More agents are not automatically faster. Stop dispatching when ownership overlaps or briefing takes longer than the remaining work.
