todo-triage

Triaging pending todos from a code review involves presenting each finding with its severity, location, and proposed solution to decide whether to approve, skip, or refine it. This process uses a structured interactive loop to map priorities to P1, P2, or P3 classifications.

Prioritizing code review tasks without writing code requires a guided triage workflow that enforces guardrails against modifications. It presents per-item details like problem scenarios and effort estimates, allowing you to approve, skip, or mark items for refinement.

Yes, you can categorize pending todos by severity and effort during triage. The interactive workflow displays these metrics alongside category, location, and problem scenario for each item, ensuring structured decision-making and accurate P1, P2, or P3 priority mapping.

An interactive todo triage workflow handles skipped or deleted items through a structured decision loop. Selecting 'next' skips or removes the finding from the queue, while progress tracking updates the overall status and moves to the subsequent pending todo.

No, you do not need to propose a solution for every todo before starting the triage process. The workflow presents existing proposed solutions during the loop, and you can choose to approve them directly, skip them, or provide custom modifications before approving.

The primary limitation of using a guided triage workflow for task tracking is the strict enforcement of guardrails against code-writing during the session. It focuses solely on reviewing, categorizing, and deciding on pending items rather than implementing the proposed solutions.