Menu
Use when parallel workers have a net benefit over coordinated sequential work.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation.
Consult before delegating implementation when an approved plan benefits from worker context isolation and durable coordination.
Consult before attempting a fix when root cause or behavior is unclear, failures repeat, components interact, or guessing would be unsafe.
Consult before implementing an observable behavior change when a meaningful automated test seam exists; use proportional red-green evidence.
Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow execution.
Consult before making a substantive completion claim; require current trustworthy evidence and semantic acceptance.
| name | dispatching-parallel-agents |
| description | Use when parallel workers have a net benefit over coordinated sequential work. |
Choose parallel work from independence, cost, coordination, and harness safety. Dispatch only when the net benefit exceeds added integration and recovery cost. Group related work when splitting it would create more reconciliation than insight.
Give each worker a bounded contract, ownership boundary, and expected evidence. Avoid shared mutable targets unless the harness coordinates them safely.
After workers return, verify the real impact boundary: shared interfaces, persisted state, user-visible behavior, and integration points their reports could miss. Isolated green results are not integration evidence by themselves.
