closing-sessionslisted

<!-- closing-sessions-version: 2 --> # Closing sessions When the user asks to close out, wrap up, or save the session, capture what is worth keeping from this conversation before it is summarised away or lost, then report what was written. Writes are autonomous: create, update, and delete happen without a confirmation prompt. Every run ends with a report of exactly what changed so the user can review with `git diff` and recover from git if a write was wrong. ## Procedure Copy this checklist and work through it: ``` - [ ] Step 1: Scan the conversation for capture-worthy material - [ ] Step 2: Classify each item by lifespan - [ ] Step 3: Dedup durable items against existing .claude/memory/ - [ ] Step 4: Write memory files and one handoff note - [ ] Step 5: Report what changed ``` ### Step 1: Scan Review the conversation since it began (or since the last time this skill ran). Collect decisions, stated preferences, constraints, references, and unfinished work. Skip anything already captured in code, git history, or CLAUDE.md, and anything that only mattered to this one exchange. ### Step 2: Classify by lifespan - Durable atomic fact -> a `.claude/memory/` file. This includes who the user is, feedback on how to work (with the why), ongoing project constraints or goals not derivable from the code, and external references (URLs, dashboards, tickets). - Transient resume state -> the handoff note. This includes what was done, what is in progress, next steps, open quest