handoff

# Session Handover (Handoff) <!-- routing-eval reads this line; it lives in the BODY so the always-on skill LISTING stays inside Claude Code's budget (1% of the context window) — an overflowing listing gets descriptions truncated or dropped, which strips the very keywords a match depends on. --> Trigger phrases: "handoff", "hand off", "session summary", "session state", "clear context", "I'll continue" ## When `/context` > 75% · phase closure · topic change. Goal: the next session should **not start from scratch**. ## Output (docs/SESSION_STATE.md, local) ``` # Session Handover — <date> ## Done - <completed work + which files> ## In progress - <what's half-finished + exactly where it was left off> ## Next step - <a clear, single high-value step> ## Open decisions - <pending decision + options> ## File pointers - docs/PLAN.md, relevant modules... ## Blockers / risks - <if any> ``` ## Measure the session before summarising it Run **`bash .claude/hooks/session-stats.sh`** first. What it reports belongs in the handover as fact, not impression — an auto-compaction means state was already dropped before you started writing (say what was lost), a runaway loop marks an approach the next session should not walk back into, and repeated prompts mark context that never landed and has to be written down explicitly this time. Missing script (plugin install) → say so. ## Principles - **Action-oriented:** focused not on "what was done" but on "exactly where to resume now." - P...