← ClaudeAtlas

session-handofflisted

Use when the user wants to hand off, transfer, pause, or continue the current session in a new session or with another agent — asks for a "session handoff", a "prompt para a próxima sessão", to "continuar de onde paramos", or invokes /session-handoff; also when context is running low and in-flight work must survive a session boundary. Produces one self-contained, copy-pasteable prompt.
will-pagane/claude-setup · ★ 4 · AI & Automation · score 72
Install: claude install-skill will-pagane/claude-setup
# Session Handoff ## Overview The next agent has **zero memory of this session**. The handoff prompt is its only inheritance — it must make that agent fully autonomous from a cold start, built from **fresh evidence, not your recollection**. **Core principle:** brief on the past, complete on the present and the future. The next agent doesn't need a changelog of how we got here — it needs to know exactly what is true *now* and what to do *next*. ## When to Use - User asks for a handoff / prompt for the next session / "continuar de onde paramos" - User invokes `/session-handoff` - Context is running low and work must cross a session boundary **Not for:** writing project docs, commit messages, or PR descriptions. Those are artifacts about the work; a handoff is an instruction set for the next agent. ## The Iron Rule: Evidence Before Writing **Never write the handoff from memory.** Your recollection drifts — commit hashes, file names, and "done" status get fabricated. Gather real evidence first, every time, even for a short session. Run and read the output of: ```bash git -C <repo> status # uncommitted / modified / untracked files — what is NOT saved git -C <repo> log --oneline -15 # recent commits — confirm hashes & messages, don't guess git -C <repo> branch --show-current git -C <repo> diff --stat # scope of uncommitted changes ``` Then review **this conversation** for: the goal, decisions made and *why*, the task in flight, blockers, and open q