handofflisted

# Handoff Compact the current session into a transient handoff doc so a fresh agent — same user, another agent, another machine, or a teammate — can pick up the work without copy-pasting context by hand. ## Invocation Position `/handoff` is a side-route skill. It is invoked ad-hoc, not from any default pipeline path. Use `/handoff` when: - a session has run long and the next step is better served by a fresh context window - you are mid-skill (mid-`/execute`, mid-`/qa`, mid-`/improve-codebase-architecture`) and the existing inter-skill compression artifacts (closing summary, research file, PRD issue, slice issue, PR) do not fit because you are not at a skill boundary - you are doing exploratory, debugging, or other non-pipeline work where no natural compression artifact exists - you want to hand off to a teammate, a different agent (Codex, Gemini, another Claude session), or a different machine Do not use `/handoff` when: - a primary pipeline skill is about to print its `**Next session:**` runtime line — that is the inter-skill compression artifact, and using `/handoff` alongside it duplicates work and creates two competing handoff records - the right move is to update an existing durable artifact: a closing summary in `/shape`, the PRD issue body, a slice issue comment with what was done and what remains, the PR body, or a `docs/solutions/` entry. State that belongs in GitHub belongs in GitHub - the session is trivial (single-question Q&A, single-file edit, copy fix) —