菜单
Use when completed work needs formal cross-stage or cross-session synthesis, resumed-task closure, durable handoff evidence, deferred-risk accounting, or an independent PR/release evidence package that the current owner's concise final response cannot represent.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a user message needs Chinese-first intent inference, low-confidence collaborative clarification, routing, workflow weight control, skill choice, review/testing/planning/debugging/evaluation routing, proactive multi-thread collaboration or conflict coordination, continuation handling, execution permission inference, or protection from process over-escalation.
Use when active development or explicit refactoring has concrete code-structure risk: a source file is accumulating independently changing responsibilities, a class/component/function is hard to navigate or test, repeated changes touch distant sections, or the user asks to split a giant file; do not use for line count alone, generated/vendor/migration/schema/fixture files, or cohesive modules that remain easier to maintain together.
Use when the user explicitly enables an automated same-project multi-thread development loop that keeps peer Codex tasks progressing, recovers conflicts or stale coordination, integrates verified work into local main, and closes cleanup without repeated gates; do not use before opt-in, for one-off coordination, remote publication without permission, or subagent creation.
Use when existing independent Codex App threads work in the same project and need peer advice, collaboration proposals, shared progress awareness, ownership arbitration, conflict pause/resume, discussion, merge coordination, status exchange, or handoff through native thread tools without creating subagents.
Use when a verified or integrated software change has concrete temporary artifacts, generated noise, stale claims, merged local branches, or disposable worktrees to clean, or when the user explicitly asks to remove development residue or old branches.
Use when the user or project rules explicitly request project-local memory/dashboard initialization or updates, or when an existing `.docs/project-memory/` is needed for cross-session recovery, durable decisions, blockers, parallel-agent coordination, or formal handoff; do not auto-initialize or sync it for ordinary development.
| name | ccdawn-completion-summary |
| description | Use when completed work needs formal cross-stage or cross-session synthesis, resumed-task closure, durable handoff evidence, deferred-risk accounting, or an independent PR/release evidence package that the current owner's concise final response cannot represent. |
| license | MIT |
把跨会话、跨 owner 或正式交接所需的现有证据压成一份可恢复的结论。普通 FAST_PATH 和有界 COMPACT_FLOW 由当前 owner 验证后直接汇报，不单独加载本 skill。
COMPLETE / PARTIAL / BLOCKED、需求覆盖、新鲜证据、未决风险和一个恢复/交付动作。ccdawn-bug-review、ccdawn-planning、ccdawn-pr-review、提交/PR 准备、ccdawn-brt 或 BLOCKED。ccdawn-brt 或更具体 owner，复合任务不吞其他 owner。下一步建议: <一个具体动作>。只在当前 owner 的简短完成说明无法承载以下任一价值时进入：
单一 owner、单一上下文、验证已通过的普通实现直接收口。缺工作回原 owner，未知根因回 Bug Review，方案边界错误回 Planning/BRT；不要用总结包装半成品。
COMPLETE / PARTIAL / BLOCKED。COMPLETE 表示目标已满足、新鲜验证通过、没有未解决 blocker；PARTIAL 表示有可恢复缺口；BLOCKED 表示继续需要新输入、权限或高风险决策。清理状态不是正式总结的固定前置条件；只有已知存在真实残留时才路由 Cleanup。
完成结论: COMPLETE / PARTIAL / BLOCKED
- 需求覆盖: <已满足；未满足/不做>
- 关键证据: <claim -> 最新证据>
- 保护边界与剩余风险: <仅真实项>
- 交付/恢复动作: <一个动作>
下一步建议: <一个具体动作>
只有跨会话恢复确实依赖持久状态时，追加最小 handoff：Owner / Completed / Evidence / Deferred / Next Action。不输出固定 Completion Gate、Review Matrix、完整 Task Graph、命令流水账或阶段菜单。