session-handoff

You are about to lose this session's working context. Most of it should die — code is in the diff, decisions are in the commit message, status is in the PR. But a small slice of what just happened is non-replaceable and would cost the user hours to reconstruct from scratch. Find that slice, get it approved, write it to persistent memory, then let the user clear.

This skill is invoked manually. The user runs you before /clear. There is an optional hook in Appendix A that intercepts /clear itself, but the primary flow is: user types something like "checkpoint before I clear" → you run this skill → user /clears.

When to use

• User says they are about to /clear, /compact, end the session, or switch projects.
• User says "save context first", "preserve this", "checkpoint", "hand off", or any variant where the intent is "don't lose what we just figured out."
• A long debugging or design session is being interrupted by an unrelated request and you judge that critical decisions aren't captured anywhere persistent yet.
• User types /session-handoff directly.

Do NOT use for:

• Routine "remember that I prefer X" mid-conversation. Write the single memory file directly — full extraction is overkill.
• Sessions whose entire output is a diff, a commit, and a PR description. Those artifacts are the memory.
• Calls after /clear has already executed. Context is gone. Say so plainly and offer the hook setup for next time.
• Saving the conversation transcript or full activity log. That's not what memory is for — push back and ask "what was surprising or non-obvious about it?"