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.
State what the next session is responsible for and which work has already been established. The request can preserve decisions, evidence, and accessible paths in a focused continuation brief, leaving unrelated conversation history outside the handoff.
Identify the feature, specification, current diff, decisions, and remaining checks.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatPreview and copy the request. It is not sent automatically from this page.
Reference: Handoff https://github.com/mattpocock/skills/blob/main/skills/productivity/handoff/SKILL.md Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: 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. Expected deliverable: A concise handoff with evidence links, current state, unresolved decisions, and the next verification steps.
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.
Implementation continuation, investigation transfer, and focused review need different handoff context. See how Handoff preserves current decisions, relevant paths, and verification evidence without passing an entire conversation history to the next agent.
Continuing implementation in a fresh session requires the current objective, settled decisions, relevant paths, and the next concrete task. Preserve the evidence that explains those choices instead of copying every conversation turn. The continuation brief should give the new session enough context to act without reconstructing the whole discussion.
An investigation handoff should point to the source paths and evidence behind its findings. Separate established facts from unconfirmed hypotheses and keep unanswered questions explicit. The next agent can then check the reasoning and continue the inquiry rather than inherit conclusions whose supporting material cannot be located.
A focused review session needs a fixed revision, bounded diff scope, and a record of verification already completed. Tailor the handoff to the code being assessed and the risks or gaps that still need attention. Avoid loading the reviewer with unrelated implementation history that does not change the review decision.
A task may stop because one question or approval remains unanswered, rather than because implementation is complete. Prepare a handoff that preserves the objective, evidence already gathered, and the exact decision needed to continue. Make the pending state explicit so the next session does not repeat finished investigation or treat an unresolved choice as permission to proceed.
A handoff is useful only when it matches the next session's responsibility. State that objective, review the generated context for missing decisions and paths, and confirm that the receiving environment can access the files needed to continue.
Describe what the next agent should accomplish and which parts of the current conversation matter.
Invoke Handoff and locate its file in the OS temporary directory. Check decisions, artifact references, and suggested skills.
Provide the document and make referenced files available to the next agent. Reconfirm anything that may have changed since it was written.
Read another Skill guide and check its original source before using it.
