mcpField
T
todo-triage

todo-triage

github.com/everyincDevelopment25.8k240 installsUpdated today
Repository

About todo-triage

todo-triage is an interactive skill for reviewing pending todo files and deciding whether to approve, skip, or revise each item. It focuses on review and prioritization, leaving implementation to `/todo-resolve`.

Key features

  1. 01Review pending todos one at a time
  2. 02Approve, skip, or modify items
  3. 03Update status and recommended action
  4. 04Track progress and summarize decisions

Use cases

  1. 01Prioritizing findings after code review
  2. 02Approving planned work before implementation
  3. 03Removing or revising proposed todos

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/everyinc/compound-engineering-plugin --skill todo-triage

After installing, type/todo-triagein Claude Code to confirm it loaded.

Details

From the project README

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

Workflow

1. Present Each Finding

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

2. Handle Decision

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.

3. Final Summary

After all items processed:

## Triage Complete

**Total Items:** [X] | **Approved (ready):** [Y] | **Skipped:** [Z]

### Approved Todos (Ready for Work):
- `042-ready-p1-transaction-boundaries.md` - Transaction boundary issue

### Skipped (Deleted):
- Item #5: [reason]
4. Next Steps
What would you like to do next?

1. run /todo-resolve to resolve the todos
2. commit the todos
3. nothing, go chill

Comments

Markdown supported