subagent-dispatchlisted

<!-- Adapted from obra/superpowers @ b36e0829: skills/dispatching-parallel-agents/SKILL.md --> <!-- Adapted to auerbachb/claude-code-config Phase A/B/C model. --> **Core principle: one agent per independent problem domain.** This skill teaches the _craft_ of designing and writing independent parallel-agent prompts. Spawn mechanics, model selection, and Phase A/B/C orchestration are in `.claude/rules/subagent-orchestration.md` — do not duplicate them here. --- ## Step 1: Decide Whether to Parallelize Run this decision tree before dispatching anything. ``` Multiple tasks? └─ Are failures/tasks related? ├─ YES (related) → Single agent investigates all └─ NO (independent) → Can they work without shared state? ├─ NO (shared state, e.g. same file) → Sequential agents └─ YES (no shared state) → Parallel dispatch ``` **Parallelize when:** - Tasks span different subsystems, files, or problem domains - Each task can be understood without context from the others - Agents will not edit the same files or shared state - The ceiling allows it (see Step 2) **Do NOT parallelize when:** - Failures are related (fixing one may fix others — investigate first) - Agents would write to the same files, branch, or session state - You don't yet know what's broken (explore first) - The pipeline ceiling is already full **This repo's vocabulary:** `/wave` calls this the "dependency- and overlap-filtered independent set"; `/subagent` calls it "disjoint chains run as pa