handoff

Write `~/.claude/custom-handoff.md` (resolve `~` to the user's home directory) summarizing current work so the next Claude session can pick up where this one left off. ## Focus argument `$ARGUMENTS`, when present, is the user's steer for what the handoff should emphasize. Let it bias every section — `GOAL`, `RECENT CONCLUSIONS`, and `NEXT` especially — toward that thread of the work. Trim or drop details unrelated to the focus, and let `NEXT` lead with the focused action. Still keep `# ORIGINAL PROMPT` verbatim; the focus reshapes emphasis, not the recorded intent. When `$ARGUMENTS` is empty, weight sections as the rules below describe. ## Steps 1. Run `trash-put ~/.claude/custom-handoff.md 2>/dev/null || true` to remove any prior handoff (ignore error if file absent). 2. Write fresh content per template. No merge, no preserve. ## Template ```markdown # ORIGINAL PROMPT <the user's opening prompt from this conversation, verbatim if short; otherwise a one-to-two-sentence summary that preserves the ask> # GOAL <one line: what we're doing now> # DONE - <thing done> - <thing done> # RECENT CONCLUSIONS - <decision, agreement, or insight from last few turns — what shifted the plan> - <open question raised at end, still unanswered> # NEXT <concrete next action — derived from RECENT CONCLUSIONS, not stale earlier intent> # WATCH OUT <gotchas; omit section if none> ``` ## Rules - Terse, scannable, under 250 words total. - `# ORIGINAL PROMPT` anchors intent across ses...