/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
- you have one item and need no worker isolation:
/rota-work - the issues are not captured yet:
/rota-capture
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.
- 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
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 with rota orchestrate or bare rota (orchestrator.harness picks the agent), or tell an existing session “you are the orchestrator”. 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.