Handoff: Carry Context Into a Fresh Session

What it does

The source writes the handoff into the operating system’s temporary directory rather than polluting the repository. It focuses on what the receiving session needs, links existing artifacts instead of duplicating them and can suggest relevant skills. Context transfer is especially useful across directories, harnesses or collaborators, where the original conversation is unavailable. Sensitive values and personal information must be removed. The document is a portable briefing; it does not itself send messages or start a new agent.

When to use it

• Move an experimental prototype’s findings back to the main project.
• Continue an investigation in a fresh context window.
• Brief a colleague on a bounded task with unresolved blockers.

Step-by-step workflow

1. Identify the receiving session’s goal and working directory.
2. Select the decisions, evidence and constraints needed for that task.
3. Reference durable artifacts rather than copying large content.
4. Write a focused temporary document after removing secrets and unnecessary personal data.
5. Provide its location and clear continuation instructions to the intended recipient.

Example request

Use handoff to prepare a new session for our CSV-import regression. Include the failing command, expected row count, files already inspected and hypotheses ruled out. Link the saved reproduction and test output rather than copying them. State that payment changes are out of scope. Use an OS temporary path and redact secrets and customer data. Do not message another task or start a session.

Worked example

A debugging handoff can say which fixture reproduces a missing row and which command demonstrates it. It should also state that a suspected delimiter issue was ruled out, preventing the next session from repeating the same work. Existing reports can be linked with their actual paths. If the recipient runs on a different machine, local links may not be usable and need an authorized transfer plan. A temporary file is useful for continuation but unsuitable as the only permanent design record.

What you get

A concise temporary handoff file with evidence pointers, constraints, unresolved questions and a specific next action.

How to evaluate the result

• Confirm the next task can start without guessing prior decisions.
• Check referenced paths exist and are reachable by the recipient.
• Review the complete handoff for confidential data.

What you need

Access to the original context and artifacts, a writable OS temporary directory and clarity about the recipient’s environment.

Setup and activation

The publisher documents plugin setup for Claude Code, Codex and Copilot, and manual Agent Skills setup for Gemini CLI and other clients. Choose one distribution method per client to avoid duplicate skills. The engineering collection expects project-specific tracker, triage-label and document-location settings from setup-matt-pocock-skills. Keep referenced companion skills and files available. This catalogue review does not install or run them; scan the exact source before any later installation. Client tools, permissions and subagent support still need separate validation.

Limits and considerations

Temporary files can disappear and local paths are not universally portable. Redact secrets and personal data. Creating a handoff does not authorize sending it elsewhere, and a suggested skill still needs compatible tools and permissions.

Related workflows

• Use prototype when moving an isolated experiment between directories.
• Use retro before clearing a session whose environment needs review.

License and reuse

MIT at repository level (Copyright 2026 Matt Pocock). Preserve the copyright and permission notice when redistributing substantial source material; inspect any separately licensed dependencies or assets.

Further reading

• Reviewed SKILL.md (immutable commit)
• Publisher README: setup and compatibility
• Reviewed MIT license