handofflisted

# Handoff Write the note yourself, while you still have the whole session in context. An automatic summary is written by something that never did the work; it keeps the topics and loses the traps. ## When to write one - The user asks for a handover. - The context window is approaching compaction. Write the note first, then keep working. After compaction it is too late; the material is gone. - The session ends with work that is not finished. A session that ends with nothing open still deserves one line saying so. That is a valid note, and it saves the next session from looking for unfinished business that does not exist. ## Where it goes `~/.agents/handoff/<agent>/YYYY-MM-DD-HHMM-<topic>.md`, where `<agent>` is the lowercase client name used in Buzz lifecycle messages (`claude`, `codex`, `pi`, ...). Create the directory if it is missing. Outside the repository on purpose. The note is session state, not project knowledge, and it would be noise in every colleague's diff. ## What it is not Three files already exist and each owns something else. Do not duplicate them: | Where | What belongs there | |---|---| | `docs/LEARNINGS.md` | Durable project knowledge, for everyone, forever. See the `reflect` skill. | | `tasks/tasks.md` | The task and its status, for everyone. | | The Buzz channel | The verified result or the concrete blocker, for everyone. | | The handoff note | What only you know right now: where you stopped, what nearly worked, which wrong turn to skip. | If