mcpField
H
handoff

handoff

github.com/tt-a1iAgent workflows192129 installsUpdated 2d ago
Repository

About handoff

handoff is an agent skill that creates a continuation document for a fresh agent, saving it in the operating system's temporary directory rather than the current workspace. It provides guidance on recording task ownership and context, suggesting relevant skills, and handling shared work safely.

Key features

  1. 01Write conversation handoff documents
  2. 02Save documents in the OS temporary directory
  3. 03Record task and repository context when known
  4. 04Suggest skills for the next agent
  5. 05Redact sensitive information

Use cases

  1. 01Transfer ongoing work to a fresh agent
  2. 02Capture ownership and worktree state for continuation
  3. 03Guide a receiver when shared-directory ownership is unclear

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tt-a1i/matt-skills-with-to-goal --skill handoff

After installing, type/handoffin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS ($TMPDIR, else /tmp; %TEMP% on Windows) - not the current workspace.

Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for.

When the facts are available, include a compact Continuation section with:

  • the exact source task ID (omit it rather than guessing),
  • the current execution owner (source, receiver, or unassigned),
  • the repository, branch, fixed point, and worktree state when relevant.

If the source and receiving sessions are existing Codex App tasks working in the same directory, suggest /codex-task-messenger. The receiver may use it to ask the source task one concrete question when the answer is not settled by the handoff or its referenced artifacts. A Messenger reply supplements the handoff; it does not replace the handoff or expand the user's authorization.

Before editing a shared directory, the receiver should confirm execution ownership once if the handoff leaves it unclear. Read-only clarification does not require an ownership transfer. If the source task is unavailable or Messenger is incompatible with the destination, continue from the handoff and referenced artifacts, surfacing only a real blocker.

Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

Comments

Markdown supported