rota

/rota-orchestrate

Run a parallel round: pick the slate, watch workers, merge their PRs.

When to use

Use on “you are the orchestrator”, “run a round”, “orchestrate”, “assign the next issues to the workers”, “what are my workers doing”.

Reach for another skill when

/rota-orchestrate
Example
rota orchestrate
run a round on issues 42, 51, 58 and 63
rota round start --scope slate --items 42,51,58,63
rota round assign 42   # claims #42, cuts <agent>/42-<slug>, starts a worker
...
Armed rota round watch in the background; it wakes me on a slot, PR or escalation change.
What changes
  • one worktree, branch and terminal tab per assigned issue
  • an orchestrator lease and slot rows in the round state
  • worker PRs that you review, gate and merge
Where this example comes from

Details

Runs a parallel round: you are the orchestrator, and standing workers (round.slots, at most as many as round.roster names) each take one issue in their own worktree and terminal tab. Start it in your existing coding-agent session with /rota-orchestrate ($rota-orchestrate in Codex). The CLI launcher is an optional alternative. The skill decides what the rota round verbs cannot: which issues make a good slate, how to read a stuck worker, what to escalate to you and when to merge. Sequencing and the rules are the verbs’ job (rota doctor, rota round start, assign, wait, rota worker gate, rota round wind-down), and a refusal from a verb is the rule, not an obstacle. Workers build and open PRs; they never merge. “You are the orchestrator” or “run a round” triggers it. For one item, use /rota-work. See parallel rounds and the rota round verbs.

When it chooses the slate it also looks for small issues that share ## Touches paths or a subsystem and proposes them as one bundle, with the lead and member order. rota round candidates marks them with bundleWith. Under autonomy.level: auto the autopilot bundles too, on declared ## Touches overlap only, for size:Minor or size:Cosmetic issues with no dependency or decision:* label, and behind round.autoBundle. See bundles.

If test setup was left open at init, the agent revisits it before assigning workers. For a new project it recommends establishing tests alongside the first implementation, so work can start while the foundation is built. Before the first merge it configures the agreed local or CI verification and requires the merge checks to pass. An explicitly agreed build or lint check is reported with that coverage, without claiming behavior tests ran. Deferral never authorizes --no-verify. Once verification is configured, later rounds do not repeat the question without a new reason. See starting without tests.

Edit this page on GitHub