cc-do
Skill1 starsChanged 7 months agoMITView on GitHub
Use when implementing planned tasks, resuming interrupted work, applying a frozen investigation handoff, or landing review feedback after cc-plan or cc-investigate.
In this repository18 other files it gives its agents.
- life-actSkill
- life-chooseSkill
- life-discoverSkill
- life-integrateSkill
- life-investigateSkill
- life-principleSkill
- life-proveSkill
- life-roadmapSkill
- life-roundtableSkill
- memory-write-gateSkill
- restart-lifeSkill
- cc-actSkill
- cc-checkSkill
- cc-investigateSkill
- cc-planSkill
- cc-roadmapSkill
- cc-simplifySkill
- cc-spec-initSkill
The file
Files
CC-Do
[PROTOCOL]: 变更时同步更新
version、CHANGELOG.md、相关模板/脚本引用,然后检查CLAUDE.md
Role
cc-do 是 PDCA 里的 Do。
同时它也是 IDCA / DDCA 里的 Do。
它只做一件事:沿着已经冻结的任务,把代码真正做出来,并把执行证据留到足够让别人接手、复盘、复验。
上游冻结合同可以来自两条路:
cc-plan产出的planning/design.mdcc-investigate产出的planning/analysis.md
Read First
PLAYBOOK.mdCHANGELOG.mdreferences/execution-recovery.mdreferences/parallel-dispatch.md
Use This Skill When
- 要实现
planning/tasks.md/planning/task-manifest.json - 执行被中断,需要恢复
- bug 根因已经在
cc-investigate里冻结,准备开始修 - review feedback 要落成代码
如果方案还没冻结、任务边界还没定,停下并回 cc-plan 或 cc-investigate。
Quick Start
先判断现在是哪一种执行局面,再开始编码:
| 现实状态 | 先走什么路径 |
| 已有 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。
Harness Contract
- Allowed actions: implement ready tasks, debug inside frozen scope, write runtime evidence, and apply review feedback that does not reopen design.
- Forbidden actions: re-planning the requirement in place, blindly rerunning the whole requirement, or delegating tasks without full task context.
- Required evidence: every task must leave red/green/review checkpoints plus objective failure notes when blocked.
- Reroute rule: after repeated failed repairs or root-cause drift, stop patching and go back to
cc-investigate; if scope or design truth breaks, go back tocc-plan; after task closure, hand off tocc-check.
TDD Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRSTcc-do 默认采用测试先行的执行纪律:
- Red:先写一个最小失败测试,运行并确认它因为目标行为缺失而失败。
- Green:只写让当前失败测试通过的最小生产代码。
- Refactor:只有 Green 之后才能清理命名、重复、结构和坏味道。
- Record:每一站都写入
checkpoint.json,必要时写入events.jsonl。
例外只能用于 throwaway prototype、纯生成文件、纯配置改动;例外必须写进 checkpoint 的 tddException,包含原因、风险和替代验证命令。测试第一次就绿,说明测试没有证明新行为,必须修测试而不是继续写生产代码。
Entry Gate
- 先读
planning/design.md或planning/analysis.md,再读planning/tasks.md、planning/task-manifest.json;如果是恢复执行,再补读最近 checkpoint 或已有handoff/resume-index.md。 - 先用
scripts/select-ready-tasks.sh判断现在到底哪几个任务真的 ready。 - 只锁定当前 ready task,或一组经依赖与触点校验后可并行的 ready tasks。
- 如果这次来自
cc-investigate,必须把planning/analysis.md当成 canonical contract,而不是一边实现一边重新调查。 - 没有任务上下文,不准把任务扔给 subagent;先用
scripts/build-task-context.sh从planning/design.md或planning/analysis.md、planning/tasks.md、planning/task-manifest.json、change-meta.json与相关 capability spec 组装上下文。
Loop
- 读取当前任务,而不是重新发明任务。
- 依赖没满足前,不准提前做下游任务。
- 没有明确并行资格,不准把多个实现任务同时推进。
- 先
fail-first:先写失败测试,先看见预期红,再写生产代码。 - 如果红灯不是预期失败(语法错、fixture 错、测试没连上),先修测试直到它正确失败。
- 按
Red -> Green -> Refactor推进,Green 只允许最小实现。 - Refactor 后必须重跑相关测试,保持 Green。
- 每次推进都写 task runtime:
events.jsonl+checkpoint.json。 - 任务实现后,先过
spec review,再过code review,两道门都过才算任务收口;这里只验证 spec delta,不回写长期 spec。 - 当前任务完成后,把可验证证据留给
cc-check。
Output
- 代码变更
- 测试变更
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 verdict
Good Output
- 当前 task 一眼可见,执行者不用从聊天记录里猜目标
- 至少留下一次明确的 Red/Green/Refactor 证据,且 Red 是预期失败
- runtime / checkpoint 足够让下一位接手者无损恢复
- reviewer 能顺着 review 记录和验证命令复盘这次实现
Bundled Resources
- 变更记录:
CHANGELOG.md - 执行 / 恢复规则:
references/execution-recovery.md - 并行分配准则:
references/parallel-dispatch.md - 恢复分析:
scripts/recover-workflow.sh - 任务状态:
scripts/check-task-status.sh - ready 任务选择:
scripts/select-ready-tasks.sh - 任务上下文组装:
scripts/build-task-context.sh - checkpoint 记录:
scripts/write-task-checkpoint.sh - review 记录:
scripts/record-review-decision.sh - 任务闭环校验:
scripts/verify-task-gates.sh - 任务勾选:
scripts/mark-task-complete.sh - 文件冲突:
scripts/detect-file-conflicts.sh
Working Rules
- 没有根因,不准修 bug。
- 没有任务边界,不准无界发散。
- 没有失败测试,不准写生产代码。
- 测试如果第一次就绿,说明你没证明任何东西,先修测试。
- 红灯原因必须和目标行为缺失一致;红灯如果只是测试写错,不算 TDD 证据。
- 先过
spec review,再过code review,顺序不能反。 - 不在
cc-do里改 capability spec 正文;这里只产出实现证据和 spec 对齐证据。 - 失败和阻塞都要留下恢复证据。
- 给 subagent 的输入必须包含:当前进度、当前任务全文、依赖状态、必读文件、验收标准、可信命令。
- 三次失败修补后必须先质疑调查合同或设计合同,而不是继续堆补丁。
Exit Criteria
- 当前任务有 Red/Green 证据
- 当前任务有
spec review/code review两道门证据 - 恢复点已更新到
devflow/changes/<change-key>/execution/tasks/<task-id>/ - 阻塞原因已写清楚
- 下一步应进入
cc-check,或明确退回cc-investigate/cc-plan
Do Not
- 不在这里重开方案讨论
- 不把一次修复膨胀成重写整个模块
- 不把依赖任务和被依赖任务同时并行
- 不把没有当前进度的任务直接丢给 subagent
- 三层以上判断说明上游合同该回炉
Companion Files
- 深入剧本:
PLAYBOOK.md - 变更记录:
CHANGELOG.md - 执行规则:
references/execution-recovery.md - 并行规则:
references/parallel-dispatch.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

