dispatching-parallel-agents

# dispatching-parallel-agents Fan out, collect everything, funnel before consuming. Plumbing other skills dispatch through — it owns the parallel discipline, not domain logic. ## Pre-flight The caller supplies the work. Confirm it, or STOP and surface the gap — never invent units or pick an agent on a hunch: - **The unit list** — N discrete, independently-completable units of work, each with its scope and target paths. - **The agent kind** — which agent kind to dispatch per unit (e.g. `backend-author`, `frontend-author`, `scout`, `security-reviewer` at [agents/<name>.md](../../agents/<name>.md)). One kind per batch. - **The completion contract** — what each agent must return: a structured result, its unit ID, and a pass/fail/error status. Self-reports are claims, not evidence (see Phase 4). ## Phase 1 — Partition · gate: BLOCK Split the work into units that do not collide. A unit owns a distinct file or path set; two units in one batch MUST NOT mutate the same path. - **Independent paths** — units touch disjoint files. Dispatch directly. This is the common, fast case. - **Shared paths unavoidable** — units must mutate the same file or tree. Do NOT dispatch into the conflict. Route to `using-git-worktrees` ([routines/using-git-worktrees/SKILL.md](../using-git-worktrees/SKILL.md)) to give each unit an isolated working tree, or serialize the colliding units into one sequential unit. A shared-path collision in a parallel batch is a corruption, not a merge. Tag each unit w...