handofflisted

# Handoff Write a document that lets a fresh agent continue this work. You are not summarising the conversation. You are writing down **the part of it that would otherwise be lost.** ## Where it goes, and why the location is not a preference Save it as a **file at the root** of `<workspace>/.claude/handoffs/` — **never inside a `<TICKET-ID>/` subdirectory.** This is mechanical, not stylistic. The `SessionEnd` hook ([`../../hooks/cleanup-handoffs.sh`](../../hooks/cleanup-handoffs.sh)) removes every subdirectory of the handoffs root and keeps the root itself: ```sh find "$HANDOFFS_ROOT" -mindepth 1 -maxdepth 1 -type d -exec rm -rf {} + ``` `-type d` is the whole story. **Directories go, root-level files stay.** A handoff written one level too deep is deleted by the hook that fires as you finish writing it, and nothing warns you — the next session simply finds nothing. Check the path before you write, not after. ## One file per subject | Case | File | |---|---| | Ticket work | `handoff-<TICKET-ID>.md` | | A topic with no ticket | `handoff-<topic-kebab>.md` | | A charted map | `handoff-chart-<slug>.md` | **A second handoff for the same subject supersedes the first. It does not sit beside it.** Two live handoffs for one subject is the failure this rule exists to prevent: the next session reads one of them, and neither file says which. **Read the existing file before you write.** Carry forward anything still live that this conversation never revisited — open questions, bl