← ClaudeAtlas

handofflisted

Write the current session down so a fresh one can carry on without the user re-explaining anything. Use when a session is getting long, running out of context, ending unfinished, or when the user says hand off, write this up, or pick this up tomorrow.
holland-built/no-yolo · ★ 0 · AI & Automation · score 72
Install: claude install-skill holland-built/no-yolo
# handoff Write a file the next session reads instead of asking the user to repeat everything. ## What it is for Context runs out mid-job and the next session starts blind. The user then re-explains what was already explained, usually badly, because the session was the one holding the detail. The handoff is what stops that — it is written for an agent to act on, not for a human to admire. ## The constraints **Write what cannot be re-derived, and skip what can.** The next session can read the code, run `git log`, and list a directory. It cannot know what was tried and abandoned, which of two readings of the request won, what broke and why, or what the user said was wanted when correcting you. That is the whole value. **Point at evidence, do not summarise it.** Real paths, real commands, real commit hashes, the exact file and line. A handoff that paraphrases its sources sends the next session hunting. **Say what is decided and what is still open, separately.** The most expensive failure here is a reopened decision — the next session re-litigates something already settled, and the user pays for the same conversation twice. Anything the user decided goes under a heading that says so. **Say what already bit you.** Every wrong turn this session took, in one line each, phrased so the next session avoids it rather than repeating it. This is the section that earns the file. **Label anything you did not check yourself.** The next session builds on this file, so a guess stated