triage-issueslisted

# Triage & groom the issue set Planning creates issues; **triage keeps them honest**. Over time priorities drift, scopes change, drafts pile up, active work loses its due date, and the `Triage` status fills with un-assessed reports. This is the recurring pass that fixes all of that — run **manually**, as a planning meeting with the operator, not on a timer. A weekly cadence is recommended, but the human pulls the trigger. `plan-feature` sets a ticket's fields at **creation**; this pass keeps them true **over time**. --- ## Posture - **Scope to the work in hand.** "Clean the board" means the milestone — or the single task — this session is already about, not every open item. Survey what that work touches, fix what drifted there, and leave the rest alone: an unrelated ticket belongs to someone else's pass, and reporting it is noise dressed as diligence. Sweep the whole board only when the operator asks for that explicitly. - **This is a planning conversation, not a batch job.** Propose field values; the operator confirms — especially **due dates**, which are commitments. Use the `resolve-pr-feedback` issue-comment loop to ask and record decisions where useful. - **Lead with priority.** Work the set in Priority order (P0 → P4). A pass outputs a clear "what's next": the P0/P1 items that aren't already moving. - **Keep the board honest.** The invariants a pass enforces: every actionable ticket has a **Type**, a **Priority**, and a **Size**; **every item that b