todo-triage

Reviews pending todo files interactively to approve, skip, or modify each work item.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill todo-triage-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: todo-triage
Source: https://github.com/mmnavarr/harness/tree/main/skills/todo-triage
Command: npx skills add https://github.com/mmnavarr/harness --skill todo-triage-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code reviews or audits generate a backlog of findings, teams need a structured way to decide which items are worth acting on. This Skill walks through each pending todo one by one so nothing is approved or discarded without an explicit decision. ## Core Features & Use Cases - Interactive Item-by-Item Review: Presents each pending todo with severity, category, location, problem scenario, proposed solution, and effort estimate, then asks for an approve, skip, or custom decision. - Status and Priority Management: Renames approved files from pending to ready, maps severity levels (P1/P2/P3) to priority tags, and deletes skipped items. - Progress Tracking and Summary: Shows progress (e.g., 3/10 completed) during triage and produces a final summary of approved versus skipped items. - Use Case: After a code review generates ten findings in the todos directory, run triage to approve the critical transaction-boundary fix, skip low-value items, and hand off the ready list to the resolution workflow. ## Quick Start Triage all pending todos in my todos directory so I can approve or skip each code review finding one by one.

Frequently Asked Questions about todo-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage pending code review findings one by one?▼

Run the triage workflow to iterate through each pending todo file, viewing its severity, category, problem scenario, and proposed solution. For each item you choose yes to approve, next to skip and delete, or custom to modify before approving.

How to prioritize todos with severity levels in a review workflow?▼

Each finding is labeled with a severity level: P1 for critical issues, P2 for important ones, and P3 for nice-to-have items. Approved items map these levels to priority tags p1, p2, and p3 in the todo frontmatter.

Where does the triage workflow read pending todos from?▼

It reads pending todos from the .context/compound-engineering/todos/ directory and the legacy todos/ directory. Each todo is a markdown file with frontmatter tracking its pending or ready status.

What happens to skipped todos during triage?▼

Choosing next on an item permanently deletes its todo file and logs it as skipped. The final summary lists all skipped items with their reasons alongside the approved ready items.

Can I implement fixes during the todo triage process?▼

No, triage is strictly for review and prioritization; writing code is explicitly disallowed during this step. Implementation happens afterward in the separate todo-resolve workflow, which consumes the approved ready todos.