handofflisted

# /handoff — Session State Persistence When invoked, write a comprehensive memory dump so future Claude sessions can resume w/o losing knowledge. ## When to use - User about to /clear and wants knowledge to persist - Context window getting heavy (>50% used) - End of long working session - Before switching projects - After major shipped milestone ## What to capture (in this order) 1. **Identity** — who user is, contacts, current location/situation 2. **Active project** — repo path, stack, deployed URL, recent changes 3. **Roadmap / locked plan** — phases, priority order, blockers 4. **Live state snapshots** — any numbers or system state the next session must not re-derive 5. **Decisions still open** — pending actions, choices waiting on user 6. **User patterns** — communication style preferences, tools used, do/don't rules 7. **Resume protocol** — exact files to read first when context restored ## Where to write **Primary:** `<repo>/.claude/SESSION_MEMORY.md` **Secondary (if applicable):** append a summary to your long-term notes store **Tertiary:** insert priority rows into Supabase `action_queue` (or equivalent task DB) so plan visible on phone/PWA ## Output format Use markdown w/ numbered sections. Heavy use of bold + tables for scannability. End w/ explicit "How to resume from clear context" checklist. ## After writing 1. List files written 2. Tell user: "Context dumped. Clear safely. Next session reads `<path>` first." 3. Suggest the 3-5 line bootstrap message