triage

• First set the /model to Haiku
• Then read all pending todos in the todos/ directory

Present all findings, decisions, or issues here one by one for triage. The goal is to go through each item and decide whether to add it to the CLI todo system.

IMPORTANT: DO NOT CODE ANYTHING DURING TRIAGE!

This command is for:

• Triaging code review findings
• Processing security audit results
• Reviewing performance analysis
• Handling any other categorized findings that need tracking

Workflow

Step 1: Present Each Finding

For each finding, present in this format:

---
Issue #X: [Brief Title]

Severity: 🔴 P1 (CRITICAL) / 🟡 P2 (IMPORTANT) / 🔵 P3 (NICE-TO-HAVE)

Category: [Security/Performance/Architecture/Bug/Feature/etc.]

Description:
[Detailed explanation of the issue or improvement]

Location: [file_path:line_number]

Problem Scenario:
[Step by step what's wrong or could happen]

Proposed Solution:
[How to fix it]

Estimated Effort: [Small (< 2 hours) / Medium (2-8 hours) / Large (> 8 hours)]

---
Do you want to add this to the todo list?
1. yes - create todo file
2. next - skip this item
3. custom - modify before creating

Step 2: Handle User Decision

When user says "yes":

1. Update existing todo file (if it exists) or Create new filename:

   If todo already exists (from code review):

   • Rename file from {id}-pending-{priority}-{desc}.md → {id}-ready-{priority}-{desc}.md
   • Update YAML frontmatter: status: pending → status: ready
   • Keep issue_id, priority, and description unchanged

   If creating new todo:

   {next_id}-ready-{priority}-{brief-description}.md
   

   Priority mapping:

   • 🔴 P1 (CRITICAL) → p1
   • 🟡 P2 (IMPORTANT) → p2
   • 🔵 P3 (NICE-TO-HAVE) → p3

   Example: 042-ready-p1-transaction-boundaries.md

2. Update YAML frontmatter:

   ---
   status: ready # IMPORTANT: Change from "pending" to "ready"
   priority: p1 # or p2, p3 based on severity
   issue_id: "042"
   tags: [category, relevant-tags]
   dependencies: []
   ---