checkpointlisted

# Checkpoint A savepoint, not a release. When a chunk of work ends, write down what a fresh session — yours, or another one after `/compact` (the step that compresses the conversation so it can keep going) — needs to pick it up without re-reading everything. The reader you are writing for is someone with **zero** context who has to be productive in five minutes. ## When to run - Right before the user runs `/compact` (or whatever the harness calls compressing the context) - Closing a phase, a milestone, a big feature - End of a long session with many commits and decisions - Context is saturated and it's time to compress Triggers: "checkpoint", "save the state", "let's wrap up", "summarize this for compacting", "let's get organized before I lose this". ## Hard rules - **Never write to git.** No `commit`, `add`, `push`, `tag`, `stash`, `branch`, `reset`. You *read* git and *report* what deserves a commit. The human — or the agent driving you — decides and executes. This is not a limitation to apologize for; it's the boundary that makes the skill safe to run anywhere. - **Git is optional.** Plenty of projects aren't repos. Every git step below degrades to a no-git path. Never fail because `git` isn't there. - **Never invent.** If you don't know what's pending, ask or leave it out. An empty section beats a fabricated one. - **Never rewrite history in the docs either.** Existing CHANGELOG entries and older checkpoints are append-only — you add, you don't edit o