菜单
Use when implementing planned tasks, resuming interrupted work, applying a frozen investigation handoff, or landing review feedback after cc-plan or cc-investigate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cc-do |
| version | 1.5.1 |
| description | Use when implementing planned tasks, resuming interrupted work, applying a frozen investigation handoff, or landing review feedback after cc-plan or cc-investigate. |
| triggers | ["开始做 T003","继续上次做到一半的任务","按 planning/tasks.md 开始实现","修这个 review comment","implement this task","resume this requirement","repair this investigated bug"] |
| reads | ["PLAYBOOK.md","CHANGELOG.md","references/execution-recovery.md","references/parallel-dispatch.md"] |
| writes | [{"path":"devflow/changes/<change-key>/execution/tasks/<task-id>/checkpoint.json","durability":"durable","required":true},{"path":"devflow/changes/<change-key>/execution/tasks/<task-id>/events.jsonl","durability":"durable","required":false,"when":"debug mode is enabled or the task execution fails"},{"path":"devflow/changes/<change-key>/execution/team-state.json","durability":"durable","required":false,"when":"execution mode uses delegated or team workers"}] |
| effects | ["code changes","test changes","workspace scratch runtime updates"] |
| entry_gate | ["Read planning/design.md or planning/analysis.md, then planning/tasks.md, planning/task-manifest.json, change-meta.json, related capability specs, and the latest checkpoint before changing code.","Select only ready tasks whose dependencies and file ownership are clear.","If the current task cannot be restated from canonical artifacts, run a context reset before coding."] |
| exit_criteria | ["The current task has red/green evidence, review evidence, and a resumable checkpoint trail.","Execution leaves the next verifier enough runtime truth to judge the task without chat memory.","The honest next step is cc-check or an explicit reroute."] |
| reroutes | [{"when":"Three failed repair attempts or new evidence show the investigation contract is wrong.","target":"cc-investigate"},{"when":"New evidence shows the requirement design or scope contract is wrong.","target":"cc-plan"},{"when":"Implementation and reviews are complete for the current task set.","target":"cc-check"}] |
| recovery_modes | [{"name":"resume-from-checkpoint","when":"Work was interrupted but the current design contract is still valid.","action":"Reload the latest checkpoint, rebuild task context, and continue from the last confirmed red/green/review milestone."},{"name":"context-reset","when":"The conversation history is noisy, stale, or cannot reproduce the exact task state.","action":"Discard chat memory, reread planning/design.md or planning/analysis.md plus planning/tasks.md/planning/task-manifest.json and the latest checkpoint, then restate the next action before coding."}] |
| tool_budget | {"read_files":9,"search_steps":6,"shell_commands":8} |
[PROTOCOL]: 变更时同步更新
version、CHANGELOG.md、相关模板/脚本引用，然后检查CLAUDE.md
cc-do 是 PDCA 里的 Do。
同时它也是 IDCA / DDCA 里的 Do。
它只做一件事：沿着已经冻结的任务，把代码真正做出来，并把执行证据留到足够让别人接手、复盘、复验。
上游冻结合同可以来自两条路：
cc-plan 产出的 planning/design.mdcc-investigate 产出的 planning/analysis.mdPLAYBOOK.mdCHANGELOG.mdreferences/execution-recovery.mdreferences/parallel-dispatch.mdplanning/tasks.md / planning/task-manifest.jsoncc-investigate 里冻结，准备开始修如果方案还没冻结、任务边界还没定，停下并回 cc-plan 或 cc-investigate。
先判断现在是哪一种执行局面，再开始编码：
| 现实状态 | 先走什么路径 |
|---|---|
| 已有 ready task，直接实现 | implement |
| 上次做到一半，需要继续 | resume |
| bug 根因已冻结 | repair-from-investigation |
| bug 还没搞清根因 | reroute 到 cc-investigate |
| 收到 review comment，要在既定范围内修正 | review-fix |
如果连“当前 task 是什么”都说不清，先别写代码，先跑 scripts/select-ready-tasks.sh 和 scripts/build-task-context.sh。
cc-investigate; if scope or design truth breaks, go back to cc-plan; after task closure, hand off to cc-check.NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
cc-do 默认采用测试先行的执行纪律：
checkpoint.json，必要时写入 events.jsonl。例外只能用于 throwaway prototype、纯生成文件、纯配置改动；例外必须写进 checkpoint 的 tddException，包含原因、风险和替代验证命令。测试第一次就绿，说明测试没有证明新行为，必须修测试而不是继续写生产代码。
planning/design.md 或 planning/analysis.md，再读 planning/tasks.md、planning/task-manifest.json；如果是恢复执行，再补读最近 checkpoint 或已有 handoff/resume-index.md。scripts/select-ready-tasks.sh 判断现在到底哪几个任务真的 ready。cc-investigate，必须把 planning/analysis.md 当成 canonical contract，而不是一边实现一边重新调查。scripts/build-task-context.sh 从 planning/design.md 或 planning/analysis.md、planning/tasks.md、planning/task-manifest.json、change-meta.json 与相关 capability spec 组装上下文。fail-first：先写失败测试，先看见预期红，再写生产代码。Red -> Green -> Refactor 推进，Green 只允许最小实现。events.jsonl + checkpoint.json。spec review，再过 code review，两道门都过才算任务收口；这里只验证 spec delta，不回写长期 spec。cc-check。devflow/changes/<change-key>/execution/tasks/<task-id>/checkpoint.jsondevflow/changes/<change-key>/execution/tasks/<task-id>/events.jsonl（仅 debug / failed 默认保留）planning/task-manifest.json 里的 task review verdictCHANGELOG.mdreferences/execution-recovery.mdreferences/parallel-dispatch.mdscripts/recover-workflow.shscripts/check-task-status.shscripts/select-ready-tasks.shscripts/build-task-context.shscripts/write-task-checkpoint.shscripts/record-review-decision.shscripts/verify-task-gates.shscripts/mark-task-complete.shscripts/detect-file-conflicts.shspec review，再过 code review，顺序不能反。cc-do 里改 capability spec 正文；这里只产出实现证据和 spec 对齐证据。spec review / code review 两道门证据devflow/changes/<change-key>/execution/tasks/<task-id>/cc-check，或明确退回 cc-investigate / cc-planPLAYBOOK.mdCHANGELOG.mdreferences/execution-recovery.mdreferences/parallel-dispatch.mdUse when verified work must be shipped or handed off with a clear landing path: run simplify and required tests, create or update a PR, prepare a local handoff, close out merged work, sync docs, write release notes, and fold follow-ups back into backlog or roadmap.
咨询式证据化自我理解入口。Use when no usable profile exists, the user says they do not know what they want, or values/talents/interests/constraints need to be refreshed before advice.
重启人生 SKILL 的前门顾问与路由器。Use when the user asks for life/career direction, confusion triage, experiment/proof/integration routing, or starts without a usable ~/.restart-life profile.
周期收尾和 durable memory 写入层。Use when proof-card review needs evidence-backed PROFILE, COMPASS, PRINCIPLES, ROADMAP, BACKLOG, versions, and next-cycle handoff updates.
原则提炼层。Use when investigation has frozen a real pain/failure/conflict case and the user needs a reusable personal principle with case evidence, counterexample, review date, and life-act handoff.
私有人生路线图层。Use when the user asks for the next months/stages, after integration changes direction, or when ROADMAP/BACKLOG need evidence-backed refresh.