orchestrate-tmux

A round is one orchestrator plus a handful of workers, running at the same time on one repository. Each worker takes a single issue in its own git worktree and its own tmux window, implements it, verifies it, opens a pull request and stops. The orchestrator assigns the issues, relays product decisions, merges the PRs and re-verifies on the main branch after every merge. Workers never merge.

That division is the whole design. Merge order, conflict resolution and post-merge verification live in one place, so no worker has to reason about what its siblings are doing, and one session is accountable for the state of the main branch.

This is the tmux version, and a good share of the mechanics below exists to reconstruct facts the multiplexer does not keep: whether an agent is working, whether it is waiting on a question, whether a keystroke landed. herdr keeps all three and reports them, so a round run on it asks instead of inferring. If that is your terminal, use orchestrate-herdr instead; the two skills are independent copies and everything above the mechanics is the same in both.