メニュー
Compact the current conversation into a handoff document for another agent to pick up.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Mandatory protocol for all pi (gpt-5.6-sol) delegation — one-off `pi` CLI calls and every workflow subagent (pi in a surfaced herdr pane via a sonnet bridge). Load BEFORE writing a Workflow script, spawning workflow workers, delegating to pi/gpt-5.6-sol, or driving herdr panes. Covers pi invocation, pane placement, report harvesting, and failure handling.
Resume work from a handoff document written by /handoff. Run in a fresh session to read the newest handoff and get briefed; run mid-session to hand off and relaunch into a fresh session automatically (via herdr when available).
Source-first external repository research using durable, human-findable local clones. Use when the user asks about an open-source repo, GitHub/GitLab URL, library internals, framework behavior, architecture, implementation details, or examples grounded in source code.
| 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 ~/.agents/handoffs/<project>/ — never the OS temp directory and never the current workspace. <project> is the basename of the git repo root (or of the current working directory when not in a repo). Create the directory if it doesn't exist.
Name the file YYYY-MM-DD-HHMM-<topic>.md, where <topic> is a short kebab-case slug of the session's focus (e.g. 2026-07-15-2150-testing-v0.1.0.md). After writing, print the full path. The companion /pickup skill resumes from the newest document in this directory.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
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.
