session-handofflisted

# Session Handoff Produce a repeatable end-of-session summary so the user can `/clear` and start a fresh agent without losing continuity. The next agent should be able to pick up by reading this document alone. This is a **context-handoff artifact**, not a status report or a retrospective. The audience is a future instance of you. Capture intent and reasoning, not implementation — anything the next agent can recover in seconds from the diff, the code, or the file itself doesn't belong here. ## When to invoke User says: "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or any near-equivalent. Also invoke proactively if the user says they're about to `/clear` without having run it yet. ## How to produce the handoff 1. **Review the whole session**, not just the last few turns. If something was compacted or truncated before this instruction ran, you can't recover it — note that under Open Questions instead of guessing or inventing it. 2. **Pull state from what you actually did:** - Plan files referenced (check `~/.claude/plans/` — `%USERPROFILE%\.claude\plans\` on Windows — if one was mentioned). - TodoWrite state — in-progress or pending tasks. - Background processes started with `run_in_background` — shell IDs are load-bearing for the next agent; without them the process is orphaned and unkillable. - Files created or modified — list what you tracked as you went. - Memory files written or update