菜单
Save comprehensive context to a handoff file for future sessions. Use when user appends #o, says "save this context", "handoff", "for next time", or when ending a session with important context. Creates a persistent record.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Budget-weighted prompt execution. depth_probe frames thinking. plan_prompt budgets effort. Per-phase pauses enable midstream metathinking. audit_probe catches gaps.
Surfaces interpretations before answering. Use when user appends #? or when question has multiple valid readings. Presents 2-3 interpretations via AskUserQuestion for selection before proceeding. For deep investigation, use mode-think.
Side-by-side comparison of options. Use when user appends #vs, says "compare X and Y", "X vs Y", "which is better", or needs to choose between alternatives. For honest yes/no verdicts, use mode-judge instead.
Gives honest evaluation without cheerleading. Use when user appends #j, asks "good idea?", "should we", "worth it?", or needs unbiased assessment. No validation theater. For challenging approaches specifically, use mode-challenge instead.
Triple-checks proposals and claims before execution. Use when user appends #p, says "check everything", "verify before doing", or when wrong execution is expensive. Three passes: facts, completeness, consequences. For post-hoc evidence proving, use mode-verify instead.
Ruthless clarification context. Use when #qh prefix detected. Interrogates assumptions and forces explicit answers before proceeding. For lighter touch, use mode-question-light.
| name | mode-handoff |
| description | Save comprehensive context to a handoff file for future sessions. Use when user appends #o, says "save this context", "handoff", "for next time", or when ending a session with important context. Creates a persistent record. |
This mode runs AFTER main work—capture context at the end. Use when important decisions, context, or progress should persist beyond this session. When composed with other modes, handoff runs last to capture everything that happened.
WHO: Context archivist ATTITUDE: Future-you will thank present-you for good notes. Capture what matters. Your job is to create a handoff document that lets a future session (or different agent) pick up where this one left off without re-deriving everything. ## Before creating handoff:Session topic: [one-line summary]
What was accomplished: [bullet list of concrete outcomes]
What's still pending: [unfinished work, blockers, next steps]
Key decisions made: [choices that shouldn't be re-litigated]
Important context: [things that aren't obvious but matter]
Create file at: `/.claude/handoffs/YYYY-MM-DD-.md`Where <slug> is 2-4 words describing the topic (e.g., auth-refactor, api-design-decisions).
File structure:
# Handoff: [Topic]
**Date:** YYYY-MM-DD
**Session:** [brief description of what this session was about]
## Summary
[2-3 sentences capturing the essential context]
## Decisions Made
- **[Decision 1]:** [what was decided and why]
- **[Decision 2]:** [what was decided and why]
## Work Completed
- [x] [Completed item 1]
- [x] [Completed item 2]
## Pending / Next Steps
- [ ] [What still needs to be done]
- [ ] [Blockers or dependencies]
## Files Touched
- `path/to/file1.py` — [what changed]
- `path/to/file2.py` — [what changed]
## Context for Future Sessions
[Anything non-obvious that future-you needs to know. Gotchas, constraints, "we tried X and it didn't work because Y".]
## Related
- [Links to PRs, issues, other handoffs if relevant]