handoff-noteslisted

# Skill: handoff-notes Compress the session into the smallest document from which someone else could continue. The failure mode is a transcript. A successor who has to read four pages to find the one broken spec would have been better off starting fresh. Aim for something a competent person reads in ninety seconds and then knows exactly what to do next. ## When to use - Context is filling mid-task and the work must continue elsewhere. - Stopping for the day mid-flow. - Passing the work to someone else. **Not** when the work is finished. Completed and committed work needs a summary, not a handoff — say what you did and stop. ## Rules 1. **Write outside the repository.** A temporary path — `/tmp/handoff-<short-name>.md` or the platform equivalent. A handoff is scratch: it must not appear in the working tree, in a commit, or in a diff someone reviews next week. 2. **Point, do not paste.** The branch by name, files by path, commits by reference, the diff by the command that produces it. Never copy file contents a successor can read themselves — that is what turns a handoff into a transcript. 3. **No secrets, no personal data.** If a configuration value matters, name the key, never the value. Assume the file will be pasted into a chat window or a ticket, because it usually is. 4. **Record decisions, not deliberation.** What was settled, so nobody reopens it. Not the reasoning that got there. 5. **State what is uncertain.** A successor acting on your guess