菜单
Preserves useful state across long agent sessions, context compaction, handoffs, and restarts. Use when compressing context, handing work between agents, resuming after interruption, writing session summaries, or preventing repeated work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Enforces a design/spec approval gate before production implementation. Use when UI, UX, product flows, architecture, API shape, prototypes, visual direction, or user-facing behaviour need signoff before builders write production code.
Keeps agent work safe in messy repositories. Use when git status is dirty, unrelated files exist, generated artefacts are present, multiple agents share a repo, or you must commit only the intended slice without damaging someone else's work.
Proves model and provider capability claims before changing agent defaults. Use when swapping models, checking context windows, reasoning effort, tool use, streaming, media support, OAuth entitlement, fallback behaviour, or provider-specific runtime paths.
Converts bug reports, screenshots, user panic, QA notes, and vague complaints into durable engineering briefs. Use when turning observed failures into reproducible issues with severity, expected behaviour, evidence, scope, owner, and acceptance tests.
Defines strict review-then-fix authority for reviewers. Use when a reviewer is allowed to repair findings after review, when avoiding reviewer-as-stealth-builder drift, or when verifying that fixes stay limited to documented findings.
Defines safe sandbox-to-production promotion gates for agent-built software. Use when deploying, restarting, promoting builds, validating runtime surfaces, checking rollback readiness, or proving that the running production artefact matches the reviewed source commit.
| name | context-continuity-handoff |
| description | Preserves useful state across long agent sessions, context compaction, handoffs, and restarts. Use when compressing context, handing work between agents, resuming after interruption, writing session summaries, or preventing repeated work. |
Use this skill when an agent session may be compressed, reset, handed off, or resumed later.
The goal is not to save everything. The goal is to save the minimum state needed to continue without repeating work or losing decisions.
Use this exact shape:
## Active Task
[Most recent unfulfilled user request]
## Goal
[One paragraph]
## Constraints
[Durable rules and user preferences that matter]
## Completed Actions
[Numbered, evidence-backed actions]
## Active State
[Repo, branch, commit, services, dirty state, running jobs]
## In Progress
[Only current unfinished work]
## Blocked
[Blocker, owner, what would unblock]
## Key Decisions
[Decisions, not every discussion]
## Resolved Questions
[Questions that no longer need asking]
## Pending User Asks
[Direct user asks still unanswered]
## Relevant Files
[Paths and why they matter]
## Remaining Work
[Concrete next steps]
## Critical Context
[Things future agent must not miss]
Preserve:
Do not preserve:
A good handoff lets a fresh agent answer: