checkpointlisted

<objective> Write a structured session-continuation memo so the next session (you, another agent, or a teammate) can resume without context-recovery overhead. You are NOT clearing context. You are NOT auto-running /clear or /compact. You write the memo, briefly confirm where it landed, and stop. The user runs /clear (or /compact, or simply leaves) themselves — except in `--mid-session` mode, where there is no clear at all. </objective> <other_skills_in_this_space> - **`/ai:checkpoint`** (this skill) — default `--to memory` writes to the user's auto-memory folder (`~/.claude/.../memory/project/`), for *future you* in the same project; pairs with `/ai:resume`. `--to tmp` writes a transfer briefing to `$TMPDIR` for another agent, machine, or teammate, with redaction always-on. - **`/gsd-pause-work`** — writes `.continue-here.md` *into the project repo* with a WIP commit. Use this in GSD projects (those with `.planning/` or `STATE.md`). Pairs with `/gsd-resume-work`. The `--to memory` path here routes to it automatically. If the project has `.planning/` or `STATE.md` and `--to memory` is selected and you do not have a strong reason to override, stop and route the user to `/gsd-pause-work` instead. `--to tmp` is not GSD-routed — a transfer briefing crosses the machine boundary, GSD pause-docs do not. </other_skills_in_this_space> <args> Parse the slash arguments before anything else: - `[slug]` (positional) — 2-5 word kebab-case topic. If absent, derive from