Back to Details

todo-triage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Todo Triage

待办事项分类（Todo Triage）

Interactive workflow for reviewing pending todos one by one and deciding whether to approve, skip, or modify each.
Do not write code during triage. This is purely for review and prioritization -- implementation happens in 
/todo-resolve
.
  • First set the /model to Haiku
  • Read all pending todos from 
    .context/compound-engineering/todos/
    and legacy 
    todos/
    directories
用于逐个审核待处理待办事项，并决定是否批准、跳过或修改每个事项的交互式工作流。
分类过程中请勿编写代码。 此流程仅用于审核和优先级排序——具体实现需在
/todo-resolve
中进行。
  • 首先将/model设置为Haiku
  • 从
    .context/compound-engineering/todos/
    目录和旧版
    todos/
    目录中读取所有待处理待办事项

Workflow

工作流

1. Present Each Finding

1. 展示每个待办事项

For each pending todo, present it clearly with severity, category, description, location, problem scenario, proposed solution, and effort estimate. Then ask:
Do you want to add this to the todo list?
1. yes - approve and mark ready
2. next - skip (deletes the todo file)
3. custom - modify before approving
Use severity levels: 🔴 P1 (CRITICAL), 🟡 P2 (IMPORTANT), 🔵 P3 (NICE-TO-HAVE).
Include progress tracking in each header: 
Progress: 3/10 completed
对于每个待处理待办事项，清晰展示其严重程度、分类、描述、位置、问题场景、建议解决方案和工作量估算。然后询问：
是否要将此事项添加到待办列表？
1. yes - 批准并标记为就绪
2. next - 跳过（删除待办文件）
3. custom - 修改后再批准
使用以下严重程度等级：🔴 P1（CRITICAL，严重）、🟡 P2（IMPORTANT，重要）、🔵 P3（NICE-TO-HAVE，锦上添花）。
每个标题中需包含进度跟踪：
进度：已完成3/10

2. Handle Decision

2. 处理决策

yes: Rename file from 
pending
-> 
ready
in both filename and frontmatter. Fill the Recommended Action section. If creating a new todo (not updating existing), use the naming convention from the 
todo-create
skill.
Priority mapping: 🔴 P1 -> 
p1
, 🟡 P2 -> 
p2
, 🔵 P3 -> 
p3
Confirm: "✅ Approved: 
{filename}
(Issue #{issue_id}) - Status: ready"
next: Delete the todo file. Log as skipped for the final summary.
custom: Ask what to modify, update, re-present, ask again.
yes： 将文件名和前置元数据中的
pending
重命名为
ready
。填写“推荐操作”部分。如果是创建新待办事项（而非更新现有事项），请遵循
todo-create
技能的命名规范。
优先级映射：🔴 P1 -> 
p1
，🟡 P2 -> 
p2
，🔵 P3 -> 
p3
确认信息："✅ 已批准：
{filename}
（问题编号#{issue_id}）- 状态：ready"
next： 删除待办文件。在最终总结中记录为已跳过。
custom： 询问需修改的内容，更新后重新展示，再进行询问。

3. Final Summary

3. 最终总结

After all items processed:
markdown
undefined
处理完所有事项后：
markdown
undefined

Triage Complete

分类完成

Total Items: [X] | Approved (ready): [Y] | Skipped: [Z]
总事项数： [X] | 已批准（就绪）： [Y] | 已跳过： [Z]

Approved Todos (Ready for Work):

已批准待办事项（待处理）：

  • 042-ready-p1-transaction-boundaries.md
    - Transaction boundary issue
  • 042-ready-p1-transaction-boundaries.md
    - 事务边界问题

Skipped (Deleted):

已跳过（已删除）：

  • Item #5: [reason]
undefined
  • 事项#5：[原因]
undefined

4. Next Steps

4. 后续步骤

markdown
What would you like to do next?

1. run /todo-resolve to resolve the todos
2. commit the todos
3. nothing, go chill
markdown
接下来您想执行什么操作？

1. 运行/todo-resolve来处理待办事项
2. 提交待办事项
3. 无需操作，休息一下