SeemSeam
SeemSeam/agent-roles-spec
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill su-reactivate命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Review a declared code change or code scope with evidence-backed findings and five independent quality scores. Use for pull requests, diffs, commits, patches, file sets, modules, bug fixes, refactors, and implementation-review requests.
Diagnose and recover a CCB agent whose provider context is corrupted, stale, overloaded, or semantically off-track when the user wants more than a plain clear: clear the agent only after safety checks, reconstruct the active task context from CCB lineage/runtime evidence, and resume or resubmit the interrupted work with a compact handoff. Use for requests like "clear this agent then restore its task", "context is broken but continue the current job", "repair talk1/worker context and inherit current state", or "after clear, recover the task".
Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, chain not continuing, rejected active-turn followup, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.
基于 SOC 职业分类
正在显示 SKILL.md
| 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 协商“旧结论是否仍有效”。如果需求、技术环境或业务优先级变化，应先回到需求分析或技术设计。
输出重新激活对象、历史原因、仍有效的内容、需要重新分析的内容和下一节点。