parallel-work-coordinatorlisted

# Parallel Work Coordinator Dispatch independent work units in parallel with sensible defaults, collect results, and reconcile findings without Workflow overhead. ## When to use - **Multi-repo sweeps:** "Audit these 4 repos for security issues" - **Multi-file operations:** "Translate these 3 document groups to PT-BR" - **Parallel investigations:** "Check these 5 error logs for the same root cause" - **Fan-out analysis:** "Review each of these 4 approach proposals for feasibility" - **When you detect sequential-by-default:** User is about to run N independent tasks one-by-one; suggest parallelism **Boundary:** If work has cross-unit dependencies (task B needs output from task A) or requires loops/conditionals, use `/loop` or the Workflow tool instead. This skill is for the happy path — fully independent units. ## Why this matters CLAUDE.md hard rule #2: "Parallel execution is mandatory for ≥2 independent tasks." But setting up Workflow requires a YAML script and cloud billing. For 3–5 independent tasks with no interdependencies, this skill provides the structure without the overhead — and enforces the mandatory parallelism. ## Workflow ### Phase 1 — Scan & Decompose Read the user's request or the active plan. Extract independent work units: - **Example 1:** "Audit repos A, B, C for security" → 3 units (one per repo, independent) - **Example 2:** "Translate files X, Y, Z to PT-BR" → 3 units (one per file group, independent) - **Example 3:** "Check logs 1–5 for root cau