handofflisted

# Session handoff A separate Claude Code window cannot read this window's conversation — sessions are not shared unless one spawned the other as an agent. So when the user pauses or switches, the only way the next session picks up cleanly is a self-contained brief. This skill writes that brief from **live, verified state**, not from what was said in chat. The whole value is accuracy: a handoff that misstates the branch, the git status, or what shipped is worse than none. Gather the real state first, then write. ## 1. Gather live state (verify, do not recall) Before writing a word, read the actual state in the working repo(s): - **Git:** current branch (`git branch --show-current`), working-tree status (`git status -sb`), position vs the remote (`git rev-list --left-right --count origin/main...HEAD`), and the last few commits (`git log --oneline -5`). If unsure whether local is fresh, `git fetch` first. - **What shipped this session:** any PRs opened/merged (`gh pr list`, `gh pr view <n>`), the commits that landed, and whether the tree is clean or has uncommitted work. - **Relevant memory:** the project's memory files already auto-load in any new session in the same repo — note which ones carry the durable plan so the next session leans on them. If any check fails or can't be verified, say so in the brief rather than guessing. ## 2. Capture these sections Keep each tight. Omit a section only if it genuinely doesn't apply. - **What we're building** — the goal,