| name | handoff |
| description | Use when the current session's work must continue in a fresh agent session — the context window is nearly full or about to be compacted, the user is ending a work session and will resume later, the work is being handed to another agent, machine, or teammate, or the user asks for a "handoff", "handoff document", "session summary to continue from", or to "prepare this for the next session". Also fires when a hook or system reminder reports high context usage and asks for a handoff. Not for writing project documentation for humans (README, docs, changelogs, reports) — only for transferring this session's state to a future agent session. |
| argument-hint | What will the next session focus on? |
Handoff
Write a handoff document summarising the current conversation so a fresh
agent can continue the work with zero access to this session's context.
The next agent knows nothing: not the codenames you invented mid-session,
not which files you touched, not why a decision was made. Write for that
reader.
Output contract
Produce one markdown document. It has exactly these parts, in this order:
- Project overview — open with the project's purpose, background,
resources, and a plain description. List the tools in play (CLIs, MCP
servers, scripts, services) and how to use each one — commands,
entry points, and any non-obvious invocation details.
- Details — policies, conventions, data structures, schemas, API
contracts, environment specifics. Everything the next agent must hold as
ground truth while working.
- Suggested skills — a named section listing the skills the next agent
should invoke, each with one line on when/why.
- Current state → open issues → what to do next — the document ends
with these three, in this order. State what is done and verified, what is
unresolved or blocked, and the concrete next steps.
