handoff
Write the current conversation into a portable handoff document for another agent to pick up.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- handoff
- license
- MIT
- description
- Write the current conversation into a portable handoff document for another agent to pick up.
- argument-hint
- What will the next session be used for?
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml150 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, outside the current workspace. Tell the user the file's absolute path, so they can open it in the next session or send it on.
Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for. Name a user-invoked skill as an instruction to tell the user to run /name ($name in Codex).
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
writing-for-agents
Writing documents for agents. Use when creating or editing skills, modifying AGENTS.md or CLAUDE.md, or writing any doc an agent reaches by a pointer.
what-would-you-do
Explain the question you just asked and recommend an answer, with the case for and against each option.
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.
wait-what
Stop. That last message did not land: re-pitch it.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
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).