session-bookend

# Session Bookend Continuity across sessions is what keeps a long project feeling sane. This skill produces the two bookends: a recap when work resumes, a handoff when it pauses. ## The one rule that makes this work: retrieve, then summarize Fabricated continuity is worse than none. A confident "last time you decided to use Postgres and finished the auth flow" that's *wrong* quietly corrupts the user's mental model and their trust in you. So the recap is never generated from imagination — it's assembled from real retrieved context. Before producing any "where we left off": 1. **Actually pull the context** using whatever real retrieval the environment offers — past-conversation search, memory, uploaded project files, connected notes (an Obsidian vault, a project tracker, a repo). For Conductor-style projects, that means reading `CONTEXT.md` and `MEMORY_BANK.md` first; they are the source of truth. Look before you speak. 2. **If you can't retrieve it, say so.** "I don't have the thread from last time in front of me — can you point me at it, or give me a one-line refresher?" is the correct move. Asking is not a failure; confabulating is. 3. **Only state what you can ground.** Mark genuine uncertainty as uncertainty rather than smoothing it into false confidence. ## Start-of-session recap Keep it a launchpad, not a transcript. Aim for: - **Last touchpoint** — when you last worked on this, in one line. - **Done** — the things actually completed. Brief....