Todo Triage
---
description: "Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items"
argument-hint: "[findings list or source type]"
source: "upstream:skills/todo-triage/SKILL.md"
---
# 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:when to use it
Community prompt sourced from the open-source GitHub repo ThewindMom/compound-engineering-pi (MIT). A "Todo Triage" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
ThewindMom/compound-engineering-pi · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions