designlisted

# /slopstop:design Stage 1 of the slopstop process. Runs on the **huge tier**. Output: a run dir under `scratch/runs/` holding `run.jsonl`, the PRD, and the charter, presented to the human at gate **G-design**. Never cuts tickets (that is Stage 2, `/slopstop:tickets`) and never implements anything. `:design` is an **orchestrator**. It launches almost nothing — subagents cannot talk to the user, and this stage is a conversation, so the grill runs inline (Step 2) — but it creates the run dir, so it writes the first lines of `run.jsonl` and owns the run's records. That makes the bracketing in Step 0c matter more here than anywhere else. - → Read `skills/run/references/run-jsonl.md` — the schema, the sole-writer rule, the human-wait bracketing, the validation invariants. Do not restate or re-invent it. **Span or note is decided by the rule there, not per stage**: a worker launch or a loop round is a span, a single atomic act is a note, and every `stage` value is one of yours. - → Read `skills/run/references/worker-launch.md` — the single `Agent()` launch form and stage → tier → model resolution, for anything this stage ever launches. **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/slopstop-run-refs/config-resolution.md` Resolve every value here, apply the documented default for any absent key, pass resolved values as explici