handofflisted

# handoff — Capture Work for a Fresh Session Write a **handoff document** that lets a new session continue this work without the current context, and file it to **mempalace** so `/vwf:recall` can retrieve it later. **When to use:** when the context window grows **beyond ~60%**, or before intentionally ending a session mid-task. A handoff written early — while the session still reasons clearly — is worth far more than one squeezed out at 95%. ## Inputs | Input | Source | | ----------- | ------------------------------------------------------------ | | `<name>` | `$ARGUMENTS` — the drawer name. Empty → the reserved `next`. | | `<project>` | the **wing**, resolved from the repo (see step 3) | | Template | `${CLAUDE_PLUGIN_ROOT}/assets/templates/handoff.md` | `$ARGUMENTS` is a short kebab-case name (e.g. `auth-refactor`). **If it is empty, the name is `next`** — never ask for one, never invent one. ## The `next` handoff `next` is a **reserved name**: the single "resume where I left off" handoff for this repo, and the default when no name is given. It differs from a named handoff in exactly three ways: - **Written to both surfaces, always.** mempalace *and* `docs/handoffs/next.md`, committed to the repo — not disk-only-on-failure like a named handoff's fallback. Either surface alone is enough to resume. - **A singleton, overwritten in place.** Each run replaces the file and supersede