session-handofflisted

# Session Handoff Generate a state-recovery document so a fresh session can resume this work without re-reading the entire conversation. The artifact is the contract between this session and the next one. ## When to trigger - **Explicit:** user says "handoff", "wrap up the session", "save state", or invokes `/session-handoff`. - **Proactive (~250K token heuristic):** you cannot count your own tokens reliably. Use proxies — if any of these have happened, surface a one-line suggestion (do NOT auto-run): - >5 large file reads - >20 tool calls in this session - the conversation has covered 3+ distinct sub-tasks - the user has said "remind me what we were doing" or similar Suggestion phrasing: *"Context is getting heavy — worth running `/session-handoff` before continuing?"* ## Modes Default mode is **conservative**. Switch to **aggressive** if the user passes `aggressive` (e.g. `/session-handoff aggressive`, or just says "aggressive handoff"). - **Conservative:** generate the artifact only. Identify durable facts that *could* go to long-term memory and list them in section 6 of the artifact for the user to approve later. - **Aggressive:** also write those durable facts to the memory system directly (if one is available), then mark each saved item `[SAVED]` in section 6. ## Process ### Pass 1 — Structured sweep (no prose) Enumerate, as raw bullet lists. Terse, one line per item: - Every file created, edited, or read (with path). - Every command/tool call run,