菜单
Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate protocol-compliant adapter stubs for Bucket 3 operations requiring external services. Use when the user requests "adapter stub", "dry run", "Bucket 3", "Linear ticket stub", "Kafka stub", or needs a fail-soft fallback for unavailable services.
Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding.
Add multi-layer validation to fix bugs caused by invalid data. Use when debugging data corruption, invalid input reaching deep execution, "defense in depth", or when a bug needs structural prevention at every layer.
Adversarial code review that iterates to convergence. Use when the user says "hostile review", "adversarial review", "tear this apart", "find all issues", or needs a thorough skeptical review of code or design.
Convert analysis results or review findings into actionable implementation plans. Use when the user says "turn insights into a plan", "prioritize findings", "action items from review", or has unstructured observations that need to become executable tasks.
Classify PRs and produce a priority-ordered merge plan. Use when the user says "merge order", "which PR first", "merge plan", or has multiple PRs targeting the same branch that need sequencing.
| name | handoff |
| description | Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session. |
Use this skill when ending a session and you want the next session to pick up where you left off. The goal is to capture enough context for seamless session continuity.
Sessions end for many reasons — context limits, breaks, or task switches. Without an explicit handoff, the next session starts cold and wastes time rediscovering state. This skill captures the current working context into a structured manifest so the next session can resume efficiently.
Capture current state. Record the essential context:
Summarize progress. Write a brief summary of what was accomplished in this session. Focus on decisions made, approaches chosen, and any non-obvious context that would be lost.
Document remaining work. List what still needs to be done, in order. Be specific — "implement the validation layer in auth.py" is useful; "finish the feature" is not.
Note blockers and warnings. Record anything the next session should know: failing tests with known causes, environment issues, dependencies on external work, or decisions that need user input.
Write the handoff manifest.
If docs/HANDOFF.md already exists, read it first and treat it as the running history. Append a new dated section (## Session — YYYY-MM-DD HH:MM) below the existing content. Do NOT delete or overwrite previous sessions — the file is a cumulative log. Update the "Remaining Tasks" and "Blockers" sections to reflect current reality (mark completed tasks as done, remove resolved blockers, add new ones). If the file does not exist, create it from scratch. The manifest should be self-contained — a reader with access to the repo but no prior context should understand what to do next.
A handoff document containing:
