fanout

# Fanout Take N units of work to N merged PRs, in parallel, without the agents colliding. **The runner is a swappable detail.** What makes this work is worktree isolation, a brief that front-loads the traps, and a merge phase that assumes conflicts are semantic. Encode those; pick whatever runner is installed. Mechanics this skill does not own: `/worktrees` for worktree lifecycle, `/herdr` for the herdr CLI, `/git` for branch and PR conventions. Compose them; do not restate them. `/delegate` is the sibling for in-process Agent-tool waves — use it when the work does not need isolated checkouts or long-running interactive sessions. ## Terminal states | State | Meaning | |-------|---------| | `SHIPPED` | Every unit merged, every issue verified closed, all worktrees removed. | | `PARTIAL` | Some units merged; the rest named with their blocker and left intact. | | `BLOCKED` | Stopped before launching. Nothing created. | | `DRY-RUN` | Plan reported; no worktree, branch, or session created. | ## 1. Group by coupling — before anything is created Do not treat the issue list as the unit list. Read each issue and find the dependencies **between** them. - If fixing A alone would create or multiply the defect B fixes, A and B are **one unit and one PR**. Splitting them ships a regression. - If two issues touch the same component, note it — they will conflict at merge. - If an issue's priority depends on an unmade decision, drop it from this run and say so rather than guessing....