session-handoff

Topics in the source

• Session Handoff
• When to write a handoff
• Where handoffs live
• Trust tags — the most important discipline here
• Writing a handoff
• Section guide
• Resume Prompt (goes at the end of every handoff)
• Resuming from a handoff

Writes and resumes structured handoff documents so work can pause in one session and resume in a fresh one — new chat, new machine, next day, different agent — without losing state, decisions already made, or mistakes already discovered. Context is degrading or approaching the token/message limit. A natural checkpoint just happened (a milestone finished, a phase wrapped up). The user is about to switch sessions, machines, or pause for the day. The user explicitly asks to "hand off", "park", or "continue later". Before a long session ends, even if not asked — better to have it and not need it. project-slug is a short lowercase-hyphenated name for whatever's being worked on (e.g. garden-redesign, q3-analysis, novel-draft). One subdirectory per project keeps unrelated handoffs from mixing when several things are in flight at once. If there's no filesystem access (e.g. plain claude.ai chat with no Claude Code project), skip the file-writing mechanics below and instead just produce the handoff content directly in the conversation, formatted per the template, so the user can copy it into their next chat. Use scripts/handofftool.py for the mechanical bits whenever a filesystem is availabl

This is an excerpt. Refer to the complete source and its current requirements.