Menu
/ccb:su-flow 的 deprecated alias；保留到 v1.5 grace window。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-plan |
| description | /ccb:su-flow 的 deprecated alias；保留到 v1.5 grace window。 |
| metadata | {"short-description":"su-flow 兼容入口"} |
/ccb:su-plan 是历史入口，语义等同于 /ccb:su-flow 的 planning 用法。v1.x 保留它是为了让旧项目和用户习惯不过早断裂。
新任务、新文档和新 UI 应优先使用 /ccb:su-flow。
默认可进入 planning 三节点：
| 节点 | Manifest |
|---|---|
| 需求分析 | references/kernel/nodes/requirement_analysis.node.md |
| 技术设计 | references/kernel/nodes/technical_design.node.md |
| 任务拆分 | references/kernel/nodes/task_breakdown.node.md |
如果用户意图超出 planning，例如要求直接派工或审查，Claude 可以提示改用 /ccb:su-flow，也可以在充分说明后进入对应节点。
/ccb:su-plan 帮我分析这个需求
/ccb:su-plan docs/02_需求设计/foo.md
等价转换：
/ccb:su-flow <同一用户意图>
本 skill 不调用 Console 业务写入接口，不读取 Console 作为业务真相源。定位上下文时先读 docs/00_项目总览.md、docs/00_文档地图.md 和 docs/.ccb/docs-structure-contract.yaml；Requirement / technical_design / dev_task 等业务文档落点必须经 docs-structure resolver / 目录契约定位，拆分草案仍写 docs/.ccb/drafts/breakdown/ 机制件。
su-plan 保留到 v1.5。v1.5 之后是否删除由用户另行拍板。保留期间：
su-plan 独有语义。/ccb:su-flow。