handoff

skills/productivity/handoff/SKILL.md · 940 B · View on GitHub at 4ae2317

Summary written at import

Writes a handoff document of the current conversation to the OS temp folder so that a fresh agent can continue, listing suggested skills and pointing to existing artifacts instead of copying them. User-invoked, mainly when work moves to another harness, folder, or person.

Files in this skill

File	What it does	Flags
agents/openai.yaml	Codex metadata for the skill: display name “Handoff”, short description “Compact a conversation into a handoff”, and policy.allow_implicit_invocation: false, which stops Codex from starting the skill on its own.

Frontmatter

name: handoff
description: Compact the current conversation into a handoff document for another agent to pick up.
argument-hint: "What will the next session be used for?"
disable-model-invocation: true

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.

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.

Original Markdown source

SKILL.md

---
name: handoff
description: Compact the current conversation into a handoff document for another agent to pick up.
argument-hint: "What will the next session be used for?"
disable-model-invocation: true
---

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.

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.