planresumelisted

# Resuming 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. ## 1. Find the checkpoint Look in `$KB/<project>/checkpoints/`, where `<project>` is the repo's folder name. Take the newest file by date in the filename. If several slugs are in play, list them with their dates and ask the user which. If there is no checkpoints directory, this is not a resume - use `/plan:run`. Read the checkpoint first. Its header names the plan and spec - read those next, then the rest of its "Read first" list, in the order it names them. Honour its staleness warnings: if it says a file is not to be trusted, do not read it for facts. If the header is missing (a checkpoint written before this was required, or by hand), find the plan yourself: strip the date from the checkpoint filename and match the remaining slug against `$KB/<project>/plans/`. The dates will not match - the plan is dated when it was written, the checkpoint when work stopped. ## 2. Verify before trusting it **The checkpoint describes the tree as it was when work stopped. Confirm it still holds before acting on it.** Things move: the user may have committed, merged, reverted, or reboot may have lost something. Check, at minimum: - `