Continue implementation elsewhere
Preserve the current objective, decisions, relevant paths, and next task without copying every conversation turn.
Handoff by Matt Pocock
Use Handoff by Matt Pocock to prepare a focused transition from one agent session to another. Summarize the current work, reference existing artifacts instead of copying them, and tailor the document to the next session’s purpose while removing sensitive details from the handoff.
Install and get started
Choose your agent to see how to get started. In Floatboat, copy a request that asks the agent to read the original instructions. Other options show the Skill installation command or the publisher’s native setup steps.
Choose an agent
Start in Floatboat
Copy the request into a Floatboat conversation
Read the original Handoff instructions at https://github.com/mattpocock/skills/blob/main/skills/productivity/handoff/SKILL.md. Explain its purpose, required tools, and installation options, then help me use it.Let the agent read the original instructions and check how to use them in your environment.
Download Floatboat ↗Try this request
Create a handoff for a fresh review session. Focus on the import feature, reference the spec and current diff, and identify the remaining verification work.
About Handoff
Handoff is a user-invoked productivity Skill in Matt Pocock’s collection. It turns the current conversation into a document that a fresh agent can use to continue the work. The source asks for references to existing specifications, plans, decisions, issues, commits, and diffs rather than duplicating those artifacts. It also includes suggested skills for the next session and uses any supplied argument to focus the handoff on the intended next task. The document is saved in the operating system’s temporary directory, not the current workspace. Review its references and sensitive information before passing it on; it does not automatically transfer session state or grant the next agent access.
Use Cases for Handoff
Explore transitions where a new session needs enough context to resume without rereading the whole conversation. Prepare an implementation continuation, hand a completed investigation to another agent, or focus a new session on review while keeping existing artifacts as the source of detail.
Pass on investigation findings
Point to captured evidence and remaining questions so the next agent can verify the reasoning.
Start a focused review session
Tailor the handoff to the review target, existing diffs, and verification already performed.
How to Prepare an Agent Handoff
State what the next session will do and invoke Handoff near the end of the current work. Review the generated temporary document, check artifact paths and omissions, and provide it to the next agent together with access to the referenced repository and files.
- 01
Name the next session’s goal
Describe what the next agent should accomplish and which parts of the current conversation matter.
- 02
Generate and inspect the document
Invoke Handoff and locate its file in the OS temporary directory. Check decisions, artifact references, and suggested skills.
- 03
Transfer context with access
Provide the document and make referenced files available to the next agent. Reconfirm anything that may have changed since it was written.
Explore More Agent Skills
Read another Skill guide and check its original source before using it.
Handoff FAQ
Does Handoff move the conversation automatically?
No. It writes a summary document. You still need to provide it to the next session or agent.
Where is the handoff saved?
The source specifies the operating system’s temporary directory rather than the current workspace. Check the returned path and retain the file if it must outlive temporary cleanup.
Should it copy every plan and diff?
The source explicitly favors referencing existing artifacts by path or URL. This keeps the handoff focused and avoids maintaining competing copies.
How can I make the next session more focused?
Pass the intended next task as the Handoff argument, such as reviewing a branch or completing one unresolved component.
Does the suggested-skills section install anything?
No. It identifies instructions the next agent may need to load. The destination environment must separately have those skills available.
Can I include credentials so the next agent can continue?
The source requires redacting keys, passwords, and personal information. Supply access through the environment’s normal credential mechanism instead.