Handoff

Compact the current conversation into a self-contained handoff document so a fresh agent — with none of this conversation's context — can pick up exactly where you left off. Work often crosses repos (backend work in one repo, then a separate agent for the frontend), and the receiving agent must be able to find the handoff without being told where to look.

Where the handoff lives (READ THIS FIRST)

The single most important thing about this skill: the handoff must be trivially findable by an agent in a brand-new context window. Do not save it to a temp dir — it would be invisible to the next agent.

Always write to .claude/handoffs/ at the current git repo's root, and tell the user the exact absolute path.

• Create the directory if it does not exist: mkdir -p <repo-root>/.claude/handoffs
• Filename convention: <from-repo>__to__<to-repo>__<short-slug>.md
  • e.g. services__to__web__teammate-invite-api.md
  • If the handoff is not repo-to-repo (same repo, just a new session), use <repo>__<short-slug>.md.
• Also maintain a pointer to the most recent handoff at <repo-root>/.claude/handoffs/LATEST.md — overwrite it each time with a one-line link to the newest handoff file plus its one-line summary. A new agent that knows nothing can always start by reading LATEST.md.

For a cross-repo handoff, the receiving agent works in a different checkout, so give it the absolute path to the file.

Tell the user how to resume