handofflisted

# /handoff Produce a concise, structured handoff document that lets a fresh session continue the current work without re-reading the whole conversation. ## Two modes **Whole-session** is the default: this session is ending, and everything in it carries forward. **Scoped** applies when the request names a subset — "hand off the API layer work", "handoff for the follow-up task that just came up". That subset leaves; this session continues without it. The rest of the conversation is not summarised, mentioned, or carried. A scope is not necessarily a single task. Work that another scoped thread depends on, or that shares its repo and background, belongs in the same document rather than a second one: one session that carries the whole chain beats two that each hold half of it, and the receiving session can hand a piece on later if it turns out not to belong. Where the scope is several threads, say so in the document — what it covers and in what order — so the next session isn't left inferring the shape of its own work. The two differ in more than emphasis, so decide which one you're in before writing anything. ## Output Emit the document as a **single fenced markdown block** in the reply, with nothing else inside the fence. That gives a one-click copy straight into a new session's opening message. Not an artifact and not a file. Both reach the same place by a longer route — open it, download it, re-upload it — when the destination is a paste into a text box. Use a fence