SeemSeam
SeemSeam/agent-roles-spec
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill su-status命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 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-status |
| description | 从 docs 人读真相源与 .ccb 协调件读取当前项目、Requirement 或子任务状态。 |
| metadata | {"short-description":"状态查看入口"} |
/ccb:su-status 用于回答“现在进行到哪里了、卡在哪里、下一步是什么”。它只读取 docs 人读真相源与 .ccb 协调件，不推进业务节点。
本指令不直接进入业务节点，但需要理解 7 节点状态：
| 节点 | Manifest |
|---|---|
| 需求分析 | 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 |
| 实施 | references/kernel/nodes/implementation.node.md |
| 审查 | references/kernel/nodes/review.node.md |
| 归档 | references/kernel/nodes/archive.node.md |
/ccb:su-status
/ccb:su-status requirement_id=<id>
/ccb:su-status task_id=<id>
展示拆分草案状态时必须通过 lib 读取并得到 hash：
import { readBreakdownDraft } from "../../lib/breakdown-draft/index.mjs";
const { draft, hash } = await readBreakdownDraft({ projectRoot, requirementId });
ValidationError 说明 draft 文件损坏或 schema drift，应报告给用户并建议 reconcile；LockTimeoutError 说明另一个 anchor 正在写，状态读取应提示稍后重试。su-status 是只读指令，严禁用 fs.writeFile 修正 docs/.ccb/drafts/breakdown/*.json。
启动/定位上下文时先读 docs/00_项目总览.md、docs/00_文档地图.md 和 docs/.ccb/docs-structure-contract.yaml。业务文档落点必须经 docs-structure resolver / 目录契约定位。
读取：
docs/03_开发计划/）docs/.ccb/events/journal.jsonldocs/.ccb/drafts/breakdown/*.jsondocs/00_文档地图.md 与 docs/.ccb/index/document-map.json不得调用 Console 业务写入接口获取状态。Console 展示只是 projection。
状态查看本身不要求 Codex 协商。若用户要求你解释状态冲突、漂移或下一步建议，应进入对应业务节点或 reconcile 类指令，而不是在 status 里直接决策。
输出当前节点、最近事件、阻塞项、命中的用户必问项、下一步建议和相关文件路径。