菜单
重新激活 cancelled/deferred 主体的大状态指令入口。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.
Fix failing tests or CI by reading logs, identifying the smallest failing surface, making a minimal change, and rerunning targeted verification. Use when given CI logs, failing commands, or broken checks.
Scan relevant source, tests, commands, and existing project patterns before editing code. Use before non-trivial implementation, bug fixing, or refactoring when the right local pattern is unclear.
Control error handling, defaults, retries, compatibility paths, and fallback behavior. Use before adding catch blocks, defaults, shims, optional values, retries, or graceful degradation.
Prevent large-file growth and mixed-responsibility edits. Use when adding significant logic to a large file, mixed-purpose module, or file with repeated conditionals.
Implement the smallest safe repo-native code change for the requested behavior. Use for feature work, small refactors, and multi-file implementation tasks.
| name | su-reactivate |
| description | 重新激活 cancelled/deferred 主体的大状态指令入口。 |
| metadata | {"short-description":"CCB 重新激活入口"} |
/ccb:su-reactivate 用于让已取消或暂缓的 Requirement / 子任务重新进入可推进状态。它必须保留历史取消/暂缓原因，不得抹掉审计。
重新激活后应根据上下文回到合适节点：
| 情况 | 建议节点 |
|---|---|
| 需求可能已过期 | references/kernel/nodes/requirement_analysis.node.md |
| 技术方案可能失效 | references/kernel/nodes/technical_design.node.md |
| 拆分草案需调整 | references/kernel/nodes/task_breakdown.node.md |
| 子任务可直接继续 | references/kernel/nodes/dispatch.node.md 或 implementation.node.md |
/ccb:su-reactivate requirement_id=<id>
/ccb:su-reactivate task_id=<id> reason="重新纳入本轮交付"
定位上下文时先读 docs/00_项目总览.md、docs/00_文档地图.md 和 docs/.ccb/docs-structure-contract.yaml。Requirement / dev_task 等业务文档落点必须经 docs-structure resolver / 目录契约定位；.ccb 只承载 state、events、draft、report、lock、index cache 等机器协调件。
reactivate 记录写入 state 和 EventJournal，不调用 Console 业务写入接口。Console 只展示重新激活结果。
重新激活必须找 Codex 协商“旧结论是否仍有效”。如果需求、技术环境或业务优先级变化，应先回到需求分析或技术设计。
输出重新激活对象、历史原因、仍有效的内容、需要重新分析的内容和下一节点。