handoff

# 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 for this handoff. **Required.** | | `<project>` | the **wing**, resolved from the repo (see step 3) | | Template | `${CLAUDE_PLUGIN_ROOT}/assets/templates/handoff.md` | If `$ARGUMENTS` is empty, ask the user for a short `<name>` (kebab-case, e.g. `auth-refactor`) and wait. Do not invent one. --- ## Pipeline ### 1. Confirm scope Restate, in one line, what work this handoff covers, so the captured state matches the user's intent. If the session spans several unrelated threads, ask which one to hand off (one handoff = one coherent thread). ### 2. Tidy & checkpoint the working state Leave the repo clean and resumable before capturing, so the handoff describes **committed** state, not a dirty tree. This runs on the **outer (superproject)** repo and its submodules — never a submodule in isola...