What problem does it solve? Coordinating a multi-session epic requires turning a planned batch of work into actually running parallel sessions, each with a complete, self-contained order — while avoiding stale chips, unmet environment blockers, and batches launched before their dependencies land. ## Core Features & Use Cases - Preflight gating: Pins the base commit, checks environment blockers, issue-body currency (needs rewrite verdicts), and merge authority before any chip is hung; held batches are reported with the exact condition that releases them. - Chip-based dispatch: Spawns one chip per batch through the host's spawn_task tool with title, tldr, cwd, and a full wave order prompt; falls back to fenced pasteable blocks where chips are unavailable. - Lifecycle management: Withdraws stale chips (dismiss_task), re-issues on fresh pins, re-issues renegotiated boundaries to every affected batch, and sequences staged waves so the next chip only goes up after the predecessor lands. - Use Case: A master session has planned an epic split into three batches across two waves. Invoke this skill to pin the base, verify no blockers hold the batches, hang one chip per batch in launch order, and report where each stands to the user. ## Quick Start From the coordinating master session, ask to launch the planned waves by hanging one chip per batch for the current epic.
