handofflisted

# Handoff Distill the current work into a **focused context package** a fresh agent can run with. A handoff is **not** a transcript summary — it's the intersection of two inputs: > The **argument** scopes the doc and picks the template (what this is about). The **current > conversation** is the source it distills. Extract from the conversation only what's relevant to > the argument; verify state claims against git and disk; never dump the whole transcript. ## Require an argument The argument names the subject. **If none was passed, stop and ask the user what the handoff should be about** — do not fall back to summarising the whole conversation. A handoff with no subject has no scope and is worthless. ## Pick the template Infer the intent from the argument and conversation, **announce which template you're using**, and let the user override: | Intent | Meaning | Template | |--------|---------|----------| | **bug** | Go *fix* this known problem | `bug-handoff.md` | | **feature-pivot** | Go *explore/build* a *new* thing we just discovered | `feature-pivot.md` | | **general** | Anything else — continue/transfer some other context | inline spine (below) | `feature-pivot` is forward-looking — a new idea surfaced in the current work, spun off for a fresh agent. It is *not* parking-and-resuming existing work. When the argument fits neither bug nor feature-pivot, use the **general** spine: > **Objective · Context · What's been done/tried · Relevant files & locations · Where i