Create Handover Prompt

Produce a lightweight, paste-ready handover PROMPT so a fresh Claude Code session can immediately continue a single task. This is the quick alternative to `/create-handover`, which writes a full multi-section handover DOCUMENT to disk for multi-phase features.

Use this when the work is a single task (not a multi-phase feature with a phase machine) and the goal is simply to ferry context into a new session by pasting a message — no persistent document, no archive lifecycle.

## When to redirect to the document instead

If the work is genuinely multi-phase, spans many sessions, or should be tracked on disk and consumed by `/resume-feature`, `/implement-next-phase`, `/phase-check`, or `/retire-handover`, tell the user that `/create-handover` (the full document) is the better fit and ask whether to use that instead. Otherwise, proceed.

## Step 1: Gather Context

Reconstruct the current state from the conversation so far plus the live repository:

- The task and its goal (what we are trying to achieve, and why).
- What has been done already, and what is still in flight.
- The concrete next step(s) — specific enough that a fresh session can start without re-deriving the plan.
- A handful of key files/paths, with line references where useful (`path:line`).
- Gotchas, constraints, decisions made, and anything easy to get wrong.
- How to verify (the relevant test/lint/run command).

Check the live state to keep the prompt accurate: `git status`, `git log --oneline -10`, and `git diff --stat`. If `$ARGUMENTS` is given, treat it as a hint about the task focus or scope to emphasize.

## Step 2: Emit the Handover Prompt

Output a SINGLE, self-contained prompt that the user can copy verbatim into a new session. Requirements:

- **Self-contained**: the pasted prompt must stand alone. Do NOT tell the new session to read an on-disk handover file or run `/resume-feature` — there is no document. Inline everything it needs.
- **Tight**: target a few hundred words. This is a prompt, not the 8-section document. Include only what the next session must know to continue.
- **Copy-pasteable**: wrap the entire prompt in one fenced code block. Use a **four-backtick** fence so any triple-backtick snippets inside survive, and prefer inline code (`` `like this` ``) for short commands.
- **Paths**: relative to the project root; be specific about files and line numbers.

Use roughly this shape inside the fenced block (adapt freely; drop empty sections):