Handoff

Process

Create a handoff document from the context and artifacts available in the current session.

Deliverable

Save it as a uniquely named Markdown file in the operating system's temporary directory, then tell the user its absolute path.

Include these sections:

1. Objective — the user's intended outcome.
2. Current state — completed work and the present status.
3. Decisions and rationale — decisions already made and why.
4. Relevant artifacts — link to files, commits, issues, specifications, plans, or URLs. Summarize essential context, but do not copy large content already available elsewhere.
5. Remaining work — ordered next actions, including acceptance criteria where known.
6. Risks and open questions — unknowns, assumptions, blockers, and required user input.
7. Suggested skills — skills that would help next, identified by name and when to use them.

Redact secrets, credentials, personal data, and other sensitive information. Explicitly note any information that was unavailable rather than inferring it.

If the user describes the purpose of the next session, tailor the objective, remaining work, and suggested skills to that purpose.