plansnapshotlisted

# Checkpointing an interrupted plan > `$KB` is your knowledge-base root: a directory outside the working repo holding > `<project>/specs/`, `<project>/plans/` and `<project>/checkpoints/`. Point at it from > your CLAUDE.md. Keeping these out of the repo keeps process artifacts from leaking > into it, and the knowledge survives clones, branches and machines. Writes `$KB/<project>/checkpoints/YYYY-MM-DD-<slug>.md`, dated the day work stopped. Same slug as the plan. Several checkpoints may accumulate for one plan; the newest is the live record. The reader is a fresh session with **no memory of this one**. Everything it needs must be in the file or named by path in it. ## The one rule **Every fact in this file is measured, now, against the tree it describes. Nothing is copied from an agent's report, and nothing is recalled from earlier in this session.** Before writing a single number, run the commands: `git log --oneline`, `git status`, the test suite, the linter. A stale checkpoint is worse than none, because the next session trusts it. If you cannot verify something, write that you could not verify it. ## Structure ### Header Two lines, before anything else. A checkpoint that cannot name its own plan is orphaned. ``` Plan: /absolute/path/to/kb/<project>/plans/YYYY-MM-DD-<slug>.md Spec: /absolute/path/to/kb/<project>/specs/YYYY-MM-DD-<slug>.md ``` Absolute paths, verified to exist. The plan and spec carry the date they were written, which is not this checkpoint's da