What problem does it solve? Multi-agent development work stalls when tickets sit in the wrong status, two sessions collide on the same work, or nobody dispatches the next stage after a gate verdict. This Skill runs the board end to end so tickets keep moving and statuses stay true. ## Core Features & Use Cases - Autonomous dispatching: Spawns stage-lead subagents directly with ticket ids, a dedicated worktree, and the seat skill, instead of handing a person commands to paste. - Collision prevention: Checks the board, worktrees, and open PRs before every dispatch or re-dispatch, and requires proof a prior agent finished before spawning a replacement. - Stage pipeline management: Moves tickets through discovery, design, build, review, and QA strictly on gate verdicts, routing defect kickbacks backwards to the owning stage. - Board hygiene and reporting: Sweeps dead worktrees, reverts automation-flipped statuses, and writes traffic-light milestone updates a non-developer can read. - Use Case: A founder asks where the milestone stands; the PM fetches main, diffs the Linear milestone against the brief, lists in-flight PRs, dispatches the next stage leads, and replies with a green/amber/red update naming every blocker. ## Quick Start Ask the agent to run the board for the current milestone and hand out the next dispatches.
