메뉴
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.
