handofflisted

# handoff Compact the current conversation into a single self-contained Markdown document that a fresh agent can read at the start of the next session and immediately know: what to do, what's already done, what's blocked, and which skills/files to touch. Save it to the OS temp directory (NOT the workspace) so it doesn't accidentally get committed. The handoff doc is a **briefing**, not a transcript. It references — never duplicates — content that already lives in other artifacts (PRs, plans, design docs, commits, memory entries, ADRs, issue trackers). *See [README.md](README.md) for the credit (Matt Pocock's original `handoff`) and install / use instructions.* ## When to invoke Fire on any of: - User invokes `/handoff` (optionally with an argument describing the next session's focus). - User says "create a handoff doc", "write a handoff document", "compact this", "pass off to another session", "checkpoint this conversation". - User says "what will the next session focus on" or "I'll pick this up tomorrow". - User signals an imminent context-window break and wants the work to survive. ## When NOT to invoke - Mid-task, when the user wants you to keep going. Handoff is a **session-boundary** ritual, not a status update mid-conversation. - For one-off questions ("what's the status?") — answer directly; don't write a file. - When the conversation is short (<20 substantive turns) and nothing material would be lost by starting fresh. - When the user is asking for documentati