todo-triage

To triage pending code review todos, step through each finding and make a deterministic decision to approve, skip, or modify before proceeding to resolution. This enforces a multi-step workflow with per-item severity handling and progress tracking.

Prioritizing and approving todos for project-wide review involves evaluating each finding's severity, category, and proposed solution, then deciding to approve, skip, or modify. A final triage summary provides next steps for coordinated implementation.

Reviewing and categorizing open code-review todos stored under .context/compound-engineering/todos involves stepping through each pending item, evaluating its problem scenario and proposed solution, and making a per-item decision to approve, skip, or modify before implementation.

Yes, handling different severity levels when triaging legacy todos and pending findings is supported. The workflow evaluates severity alongside category, description, and location for each item, guiding deterministic decisions to approve, skip, or modify before resolution.

Yes, the todo triage workflow tracks progress throughout the per-item decision process and outputs a final triage summary. This summary includes next steps to coordinate review before proceeding to the actual resolution implementation.

You should skip a todo during the code review triage process when the finding is not ready for implementation or requires further evaluation. Skipping defers the item, allowing you to approve or modify only the pending todos that are ready for resolution.