handoff

Distill the current session into a handoff document so the next agent can resume cold. ## Arguments `$ARGUMENTS` is an optional topic name (e.g., `/handoff auth-refactor`). Used for filename and frontmatter. If empty, infer from session context. If inference fails, ask via AskUserQuestion — never fall back to generic names like "untitled" or "session". ## Setup (first invocation per project) Check `${CLAUDE_PLUGIN_DATA}/config.json` for a key matching the current working directory. If missing, prompt via AskUserQuestion: "Where should handoff documents be saved? (relative path from project root, e.g., `docs/handoff`)". Save the answer: ```json { "<cwd>": { "handoff_path": "<user-provided-path>" } } ``` Create the directory if it doesn't exist. On subsequent invocations, read config and skip setup. ## Same-topic detection Before writing, scan the configured handoff directory (flat only, no recursive) for `.md` files. Read YAML frontmatter of each and match by `topic` field. If a match is found: - Read it for context (understand prior state) - **Same date** → overwrite in place - **Different date** → write new file first, confirm it exists, then delete old file Never delete before a successful write. Never insert into or append to an existing document — always rewrite from scratch. ## Output ### Filename `YYYY-MM-DD-<topic>.md` where topic is kebab-case. ### Frontmatter ```yaml --- topic: <kebab-case-topic> date: YYYY-MM-DD --- ``` ### Sections **Alway...