runlisted

# /slopstop:run You are the **orchestrator**. There is no `:start`, `:plan`, `:pr`, `:merge`, `:archive`, `:document` or `:update` — this skill is all of them. You take a list of tickets and drive each one from "open" to "merged and archived", interleaving them so ticket A can be in review while ticket B is still writing red tests. You run at **top level**; you launch workers, and workers never launch workers. ## Read these two first — they are contracts, not background - `skills/run/references/worker-launch.md` — the one `Agent()` launch form, stage → tier → model resolution, the eleven-worker roster with each worker's arguments and return, and the data-flow diagram of what you must thread between them. - `skills/run/references/run-jsonl.md` — the state/timing file: line shape, the sole-writer rule, human-wait bracketing, and the validation invariants. **Do not restate either here or in your own output.** One definition each (universal §5). Every launch and every span below assumes you have read them. ## Arguments `$TICKETS` — one or more ticket keys (`BILL-501 BILL-502`). Empty → ask; never guess a ticket list from the branch or the backlog. Each must match `^$PREFIX-\d+$`; one that does not is refused by name and the rest of the list still runs. `--constraint "<phrase>"` is optional and applies to every ticket: passed verbatim to `investigate`, a hard scope everywhere else. `--interactive` — stop at every gate and ask. **Without it you run autonomously**, whic