Back to Details

ce-todo-resolve

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Resolve approved todos using parallel processing, document lessons learned, then clean up.
Only 
ready
todos are resolved. 
pending
todos are skipped — they haven't been triaged yet. If pending todos exist, list them at the end so the user knows what was left behind.
通过并行处理解决已获批的待办事项（todos），记录经验教训，然后进行清理。
仅处理状态为
ready
的待办事项，跳过
pending
状态的待办事项——它们尚未完成分类。若存在pending状态的待办事项，需在末尾列出，让用户了解未处理的内容。

Workflow

工作流

1. Analyze

1. 分析

Scan 
.context/compound-engineering/todos/*.md
and legacy 
todos/*.md
. Partition by status:
  • ready
     (status field or 
    -ready-
    in filename): resolve these.
  • pending
    : skip. Report them at the end.
  • complete
    : ignore, already done.
If a specific todo ID or pattern was passed as an argument, filter to matching todos only (still must be 
ready
).
Residual actionable work from 
ce-code-review mode:autofix
after its 
safe_auto
pass will already be 
ready
.
Skip any todo that recommends deleting, removing, or gitignoring files in 
docs/brainstorms/
, 
docs/plans/
, or 
docs/solutions/
— these are intentional pipeline artifacts.
扫描
.context/compound-engineering/todos/*.md
和旧版
todos/*.md
文件，按状态分类：
  • ready
    （状态字段或文件名包含
    -ready-
    ）：处理这些待办事项。
  • pending
    ：跳过。在最后报告这些待办事项。
  • complete
    ：忽略，已完成。
如果传入了特定的待办事项ID或模式作为参数，仅筛选匹配的待办事项（仍需处于
ready
状态）。
ce-code-review mode:autofix
在
safe_auto
阶段完成后产生的剩余可执行工作，其对应的待办事项已处于
ready
状态。
跳过任何建议删除、移除或通过git忽略
docs/brainstorms/
、
docs/plans/
或
docs/solutions/
目录下文件的待办事项——这些是有意保留的流水线产物。

2. Plan

2. 规划

Create a task list grouped by type (e.g., 
TaskCreate
in Claude Code, 
update_plan
in Codex). Analyze dependencies -- items that others depend on run first. Output a mermaid diagram showing execution order and parallelism.
创建按类型分组的任务列表（例如Claude Code中的
TaskCreate
、Codex中的
update_plan
）。分析依赖关系——优先执行被其他任务依赖的项。输出一个mermaid图表，展示执行顺序和并行关系。

3. Implement (PARALLEL)

3. 执行（并行）

Spawn a 
workflow:ce-pr-comment-resolver
agent per item. Prefer parallel; fall back to sequential respecting dependency order.
Batching: 1-4 items: direct parallel returns. 5+ items: batches of 4, each returning only a short status summary (todo handled, files changed, tests run/skipped, blockers).
For large sets, use a scratch directory at 
.context/compound-engineering/ce-todo-resolve/<run-id>/
for per-resolver artifacts. Return only completion summaries to parent.
为每个任务启动一个
workflow:ce-pr-comment-resolver
Agent。优先使用并行处理；若存在依赖关系，则按依赖顺序串行执行。
批量处理规则：1-4个任务：直接并行返回结果。5个及以上任务：每4个为一批，每批仅返回简短状态摘要（待办事项处理情况、修改的文件、运行/跳过的测试、阻塞问题）。
对于大规模任务集，在
.context/compound-engineering/ce-todo-resolve/<run-id>/
目录下创建临时目录，用于存储每个解析器的产物。仅向父进程返回完成摘要。

4. Commit & Resolve

4. 提交与标记完成

Commit changes, mark todos resolved, push to remote.
GATE: STOP. Verify todos resolved and changes committed before proceeding.
提交变更，标记待办事项已完成，推送到远程仓库。
检查点：停止操作。在继续之前，验证待办事项已标记完成且变更已提交。

5. Compound on Lessons Learned

5. 总结经验教训

Load the 
ce-compound
skill to document what was learned. Todo resolutions often surface patterns and architectural insights worth capturing.
GATE: STOP. Verify the compound skill produced a solution document in 
docs/solutions/
. If none (user declined or no learnings), continue.
加载
ce-compound
技能，记录所学到的内容。待办事项的处理过程通常会浮现值得记录的模式和架构见解。
检查点：停止操作。验证
compound
技能已在
docs/solutions/
目录下生成解决方案文档。如果未生成（用户拒绝或无经验可记录），则继续。

6. Clean Up

6. 清理

Delete completed/resolved todo files from both paths. If a scratch directory was created at 
.context/compound-engineering/ce-todo-resolve/<run-id>/
, delete it (unless user asked to inspect).
Todos resolved: [count]
Pending (skipped): [count, or "none"]
Lessons documented: [path to solution doc, or "skipped"]
Todos cleaned up: [count deleted]
If pending todos were skipped, list them:
Skipped pending todos (run /ce-todo-triage to approve):
  - 003-pending-p2-missing-index.md
  - 005-pending-p3-rename-variable.md
从两个路径中删除已完成/已处理的待办事项文件。如果在
.context/compound-engineering/ce-todo-resolve/<run-id>/
创建了临时目录，则删除该目录（除非用户要求保留以供检查）。
已处理的待办事项数量：[count]
已跳过的待办事项（pending状态）：[count，或"无"]
已记录的经验教训：[解决方案文档路径，或"已跳过"]
已清理的待办事项文件数量：[count]
如果存在被跳过的pending状态待办事项，列出它们：
已跳过的pending状态待办事项（运行/ce-todo-triage命令以批准）：
  - 003-pending-p2-missing-index.md
  - 005-pending-p3-rename-variable.md