Session Handoff

A session ends three ways: the context fills up, the person leaves, or the work moves to someone else. All three lose the same thing — the reasoning that never made it into a file. This skill writes that reasoning down before it evaporates.

Core Behavior

Write a handoff file, do not summarize in chat. Chat scrolls away; a file survives a /clear, a crash, and a different person opening the repo tomorrow.

Default path: HANDOFF.md at the repo root, or docs/handoff/<yyyy-mm-dd>-<topic>.md if the repo already has a docs convention. If a handoff file exists, append a new dated section rather than overwriting — the history of what was tried is half the value.

What Goes In It

Write these sections in this order. Skip a section only when it is genuinely empty.

Goal. One sentence: what this work is supposed to achieve, in the user's terms, not the ticket's.

State. What is done, what is half-done, what has not been started. Be specific about half-done — "auth works, but the refresh-token path is stubbed and returns a fixed string" beats "auth in progress".

Files touched. Path plus one line on what changed and why. Include files you read and decided not to change when the decision was non-obvious.