← ClaudeAtlas

session-handofflisted

Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or wants a structured end-of-session summary before clearing context. Also use proactively when the user says they are about to /clear and no handoff has been produced yet. Generates a handoff document saved as a file (in the project's docs/handoffs/ directory, or as a downloadable file in chat environments) with required sections (objective, status, decisions + rationale, key files, next action) plus situational sections included only when they apply, so a fresh agent can continue seamlessly without re-deriving lost context.
AdityaVasireddy/agent-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill AdityaVasireddy/agent-skills
# Session Handoff Produce a repeatable end-of-session summary so the user can `/clear` and start a fresh agent without losing continuity. The next agent should be able to pick up by reading this document and the files it points to, in the order it declares — the handoff is the entry point to the chain, not a replacement for it. This is a **context-handoff artifact**, not a status report or a retrospective. The audience is a future instance of you. Capture intent and reasoning, not implementation — anything the next agent can recover in seconds from the diff, the code, or the file itself doesn't belong here. ## When to invoke User says: "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or any near-equivalent. Also invoke proactively if the user says they're about to `/clear` without having run it yet. ## How to produce the handoff 1. **Review the whole session**, not just the last few turns. If something was compacted or truncated before this instruction ran, you can't recover it — note that under Open Questions instead of guessing or inventing it. 2. **Pull state from what you actually did.** These are the categories to sweep; the tool that produces each one varies by runtime, so capture the category even when the named tool doesn't exist here: - **Plan or spec file** that drove the session (in Claude Code, check `~/.claude/plans/` — `%USERPROFILE%\.claude\plans\` on Windows — if one was mentioned). -