What problem does it solve? Coordinating multiple AI coding agents on a feature's ticket backlog is error-prone: claims collide, parallel edits conflict, and finished work goes unreviewed. This Skill provides a single-orchestrator loop that claims tickets, spawns worker agents in isolated git worktrees, integrates their branches, and routes every build through a user ruling before merge. ## Core Features & Use Cases - Ticket DAG orchestration: Computes the frontier of unblocked tickets from blocked-by dependencies, plans parallel waves based on file-overlap and surface-coherence analysis, and spawns one worker per ticket on local or remote (SSH) hosts. - Review-gated integration: Workers flip tickets to review when done; the orchestrator reads the diff, presents a review page, and merges only on user accept, with amend, redo, and reject paths. - Failure recovery: Probes worker sessions, resumes stopped workers with guidance, resets unrecoverable sessions to open, and re-arms watchers after orchestrator restarts. - Use Case: A feature spec has been broken into eight tickets. Run dispatch to work them serially or in waves: each ticket gets its own worktree and worker agent, landed branches merge into the feature branch, and the feature closes with a whole-feature code review, hardening pass, and debrief. ## Quick Start Say "dispatch the tickets for this feature" after creating tickets with the tracker workflow, and the orchestrator will claim, spawn, integrate, and report until the feature ships.