handoff
Compact the current conversation into a handoff document for another agent to pick up.
- License 许可
- MIT
- 最近更新
- 2026-10-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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
- false
02 资源文件 1
- 参考文档agents/openai.yaml141 B
03 SKILL.md 正文
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 - not the current workspace.
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.
04 同仓库更多 Skills
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
oio-review-artifact
Generate or revise interactive OIO HTML review artifacts and linked review packages for Outcome Definitions, Will / Will Not records, specifications, architecture records, audits, learning records, and other component-level Human approvals. Use when OIO material needs Agree / Revise / Question controls, pending-only filtering, comments, copyable review receipts, print-to-PDF, fingerprints, manifests, or a Sites-ready review surface. Do not use for unrelated websites or generic documents.
oio-local
Guide a nondeveloper through an outcome-first local implementation in Codex or Claude Code. Use when the Human asks OIO Local to set up a project or produce a substantial file-, tool-, or implementation-based result.