菜单
Use when a session is ending, context needs to be preserved for a future session, or when transferring work between agents. Generates a structured handoff document with open questions, next steps, and context summary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when debugging a failing test, broken build, runtime error, or unexpected system behavior. Drives hypothesis-based investigation, root-cause fixes, verification, and reusable learning capture.
Use when a claim, plan, spec, doc, or design must be attacked against source evidence before implementation or approval. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when fixing broken behavior and the priority is reproduce, root cause, regression proof, and the smallest safe repair. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when reviewing code changes with explicit stage, target, and focus so own-code checks and others’ PR reviews stay distinct but share one contract. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when the deliverable is docs or reference material and every claim must stay tied to observed behavior or cited source evidence. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when adding or changing product behavior that must ship with explicit purpose, scenarios, and verification. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
| name | handoff |
| description | Use when a session is ending, context needs to be preserved for a future session, or when transferring work between agents. Generates a structured handoff document with open questions, next steps, and context summary. |
Use this skill when:
Do not use for trivial completions (single file edit, quick fix). Do not use when the work is fully done — a simple summary in chat is sufficient.
A handoff is a single markdown document stored in the durable memory system. It must answer three questions for the next agent: What was done? What is blocked? What should happen next?
Assess handoff necessity
Gather context
Write the handoff document with this exact structure:
# Handoff: [Brief Title]
**Date:** [ISO 8601]
**From:** [agent/session identifier]
**Status:** [in_progress | blocked | pending_review]
## Work Completed
- [ ] [Specific accomplishment with file path]
- [ ] [Another accomplishment]
## Open Questions
1. [Question that needs answering before next step]
2. [Another question]
## Next Steps
1. [ ] [Concrete next task with acceptance criteria]
2. [ ] [Another task]
## Context for Next Agent
- **Branch:** [current git branch]
- **Uncommitted changes:** [yes/no + brief description]
- **Blocked by:** [whats blocking progress, or "none"]
- **Key files:** [list of files the next agent must read first]
## Technical Notes
- [Tool/dependency version if relevant]
- [Configuration that changed]
- [Known issues or gotchas]
Store the handoff
ai-memory or similar durable store is available: store there with tag handoff-[date]specs/memory/handoffs/[YYYY-MM-DD]-[title].mdNotify
in_progress, blocked, pending_reviewmemory-promotion — For elevating ephemeral notes to durable knowledgeskill-authoring — For turning handoff patterns into reusable skills