Handoff

Handoff

Compact the current conversation into a handoff document for another agent to pick up. Save it under the operating system's temporary directory, never in the current workspace.

This skill creates a portable artifact. It does not create, fork, navigate, or transfer a Codex task and does not mutate the worktree.

Workflow

1. Treat any user arguments as the next session's focus and tailor the document to that recipient. Otherwise target a fresh general-purpose agent.
2. Extract only the resumable thread: objective, confirmed decisions, current state, remaining work, blockers, and material unknowns.
3. Inventory existing artifacts such as specs, plans, ADRs, issues, commits, diffs, test output, and URLs. Reference them instead of copying their settled content.
4. Redact secrets and sensitive personal information before writing. Replace a removed value with [REDACTED] only when the receiver needs to know that a value exists.
5. Create the Markdown file with an OS secure temporary-file primitive such as mktemp or an equivalent API. Require a newly created regular file, refuse symlinks, use an unpredictable name, and keep permissions owner-only (0600 or the platform equivalent) before writing content.
6. Return the absolute path and a one-line description of the intended next step.

Document Contract

Use only the sections that carry useful state, except Suggested skills, which is required. If no installed skill materially helps the receiver, write None instead of inventing one.

# Handoff: {short task name}

## Target
{Who or what the next session is for}

## Objective
{The concrete outcome and completion criteria}

## Live context
{Conversation-only decisions and reasoning not already captured elsewhere}

## Current state
{Completed, in progress, verified, and unchanged}

## Next actions
{Ordered, executable continuation steps}

## Blockers and unknowns
{What must be decided or verified; distinguish fact from inference}

## Suggested skills
{Only skills the receiving agent should actually invoke, with why}

## References
{Paths, URLs, commits, diffs, and access caveats}

Do not paste the transcript, full source files, large diffs, or artifact contents. Do not claim tests passed or work completed without evidence from the conversation or referenced artifacts. If a material fact is unavailable, mark it unknown.

When another workflow calls this skill, preserve that workflow's vocabulary and identifiers. For example, a review handoff should carry each finding's ID, disposition, claim, and evidence reference or locator; each unresolved finding should also carry its next check. Include verification, review URL, and remaining acceptance criteria. Reference the reviewed artifact rather than embedding it.