Handoff

Run only on an explicit handoff request, including a runtime-expanded invocation. Package the context another session needs; stop after returning the document. Suggested skills are recommendations, not invocations or authorization. Creating a handoff launches no agents and grants no implementation, tracker, merge, deployment, release or installation permission.

Read validation when changing or validating this package.

1. Bound the transfer

Identify the destination task, target project and intended audience from the request and conversation. Use any arguments as the next session's focus. If that focus is unclear, ask one focused question before writing. Read applicable project instructions and retention/disclosure rules. Separate confirmed decisions and their rationale from proposals, assumptions and unresolved questions.

For immediate local transfer, default to a uniquely named Markdown file in the OS temporary directory ($TMPDIR, otherwise /tmp; %TEMP% on Windows). Use the runtime's safe temporary-file facility rather than a predictable shared filename. Temporary files may disappear and may be inaccessible from another harness or machine. For later resumption or another destination, use an explicitly approved durable location; if none is approved, ask for one or return a conversation-only draft with the storage gap. Keep the file out of the workspace by default. Preserve existing files and use access restricted to the current user where supported.

Done: focus, audience, authorized content and destination are known, or the missing decision is reported without writing a file.

2. Capture the live thread

Inspect the relevant existing artifacts and current state through authorized read-only access. Reference specs, plans, ADRs, issues, commits, diffs and evidence by path or URL instead of copying them. Record the project root or repository identity needed to resolve paths, relevant revision or observation time, and any destination access limitation. A local path is not portable merely because it appears in a document: flag references the receiver cannot access and propose an approved transfer or durable pointer. Never upload artifacts as a side effect.

Write only sections useful for the next task: