resumelisted

# /resume — Pick up from a prior checkpoint The user just started a fresh session and wants to continue from where the previous session ended. There is a checkpoint file waiting for you. ## Step 1 — Find the candidate checkpoint(s) The current project's slug is the basename of the CWD. Checkpoints live at `~/.claude/checkpoints/<project-slug>/`. List all checkpoints for this project, newest first, and grab the current time so you can label them accurately later: ``` ls -t ~/.claude/checkpoints/$(basename "$PWD")/*.md 2>/dev/null; date ``` Hold onto the `date` output — you'll subtract from it in Step 1a to produce relative-time labels. The system reminder gives you today's *date* but not the current *clock time*, so without `date` you'll guess and get it wrong (e.g. labeling a 5-minute-old checkpoint as "2h ago"). Branch on the count: - **0 files** — no checkpoint matched. Check `~/.claude/checkpoints/` to list all available project subfolders, in case the user is in a different CWD than when they checkpointed (e.g. they checkpointed from `<workspace-root>/jessica` but ran `/resume` from `<workspace-root>/jessica/pipeline`). Tell the user no checkpoint was found for this project, list what *is* available, and ask which to load (or to start fresh). - **1 file** — load it directly. Skip Step 1a and proceed to Step 2 with that file. - **2+ files** — go to Step 1a to let the user pick. (The user sometimes runs parallel VS Code conversations rooted in the same project folder