dispatch-parallellisted

# /dispatch-parallel — Safe Parallel Subagent Dispatch > **Announce on start:** open your reply with "Using /dispatch-parallel to fan out N tasks after the Conflict Radar check." Dispatch 2+ coding subagents in a single message with `isolation="worktree"`. Verifies the 4-layer Conflict Radar (see `docs/playbooks/parallel-conflict-prevention.md`) before dispatching. ## Token budget (MANDATORY) - Read each task's design doc with `limit: 120` — header + Touched Files matrix only. - Conflict Radar is grep-based — no full reads. - Do NOT re-read CLAUDE.md (auto-loaded by the harness). ## Invocation ``` /dispatch-parallel <task-id-1> <task-id-2> ... <task-id-n> ``` The skill reads each task's design doc, extracts the declared paths, runs Conflict Radar, then either dispatches in parallel (overlap-free) or refuses and suggests serialization. ## Steps 1. **Read each task's design doc** For each task ID `{{TASK_ID_PREFIX}}-S<N>.<NN>`: ``` Read docs/designs/sprint-S<N>/D<NNN>-<slug>.md (limit: 120) Extract: declared touched-files matrix, dependencies (blockedBy), subagent_type ``` 2. **Conflict Radar Layer 1 — Path overlap check** For each pair of tasks, intersect their declared paths. If any pair intersects → SERIALIZE (refuse parallel dispatch). - Allowed: tasks touching different components / different modules. - Forbidden: two tasks both editing the same file or the same shared package. 3. **Conflict Radar Layer 1b — Working-tree state overlap