ticketslisted

# /slopstop:tickets Stage 2 of the slopstop process. **This skill is an orchestrator**: it launches timed work as agents, and it records every transition in `run.jsonl`. Input: the run dir a `/slopstop:design` session produced. Output: an adversary-approved ticket tree in the project's ticket system, presented at gate **G-tickets**. It never launches implementation work — that is `/slopstop:run`. ## The two shared contracts — read both before doing anything Both are binding, and neither is restated here (universal §5, one definition): - **The timing/state file** — schema, sole-writer rule, human-wait bracketing, validation: → Read `~/.claude/commands/slopstop-run-refs/run-jsonl.md` - **The worker launch form** — the single `Agent()` shape, model resolution, the roster: → Read `~/.claude/commands/slopstop-run-refs/worker-launch.md` Two consequences that govern every step below: - **You are the sole writer of `run.jsonl`**, at `scratch/runs/$RUN_ID/run.jsonl`. No worker writes it, no worker resolves a path. A worker returns a result; you stamp it. **Your stages follow the same span-vs-note rule** — a worker launch or a loop round is a span; a single atomic act is a note. Do not re-derive it per stage, and do not invent a `stage` value that is not one of yours. - **You are the sole reader of the resolved configuration** — three sets, defaults → `.project-conf.toml` → gitignored `.project-conf-local.toml`, merged per leaf key. → Read `~/.claude/commands/slo