handoverlisted

# handover The problem this solves: a long Claude Code session ends, and everything it learned evaporates. The next session starts cold and re-derives context you already paid for. But the fix people reach for - dumping the whole session into a running log - is worse, because now the next session has to read 300 lines to find the 5 that matter. This skill draws one line: **what does the NEXT session actually need to resume, and nothing else.** Everything durable gets routed to a permanent home instead. What's left is a short, disposable note that gets overwritten every run and never accumulates. Designed for stateful, multi-session work - the kind where you're mid-build across several sittings and the state doesn't fit in your head. ## Configure once The skill routes durable knowledge out of the handover and into permanent stores. Point these at wherever yours live (edit this block, or tell the session at runtime): ``` MEMORY_STORE = ~/.claude/ (or your Claude Code memory directory) KNOWLEDGE_BASE = (optional) a wiki, notes vault, or docs folder for world-state and cross-project decisions ``` If you don't keep a separate knowledge base, fold that routing into memory. The principle holds regardless of where the stores physically are. ## Step 0 - Confirm there's anything to hand over If git is clean, nothing is half-finished, and no decision/constraint/open question surfaced this session, tell the user there's nothing to hand over and stop. Do not wr