triage-issuelisted

# Triage Issue (IRP T0-T8) Run a full IRP triage on a GitHub issue: search knowledge base, create a mission, and assign actionable tasks. --- ## WORKFLOW **T0 — Identify the issue** If the user provided an issue number, use it. Otherwise ask: "Which issue number should I triage?" Fetch the issue: ``` gh issue view {number} --json number,title,body,labels,assignees,milestone,state ``` Extract: title, body, labels, current assignees, milestone. **T1 — KB search (silent)** Search VantageMemory for relevant prior context: - `mcp__vantage-peers__recall` query: "{issue title}" namespace: global, limit: 5 - `mcp__vantage-peers__recall` query: "{key labels joined}" namespace: global, limit: 5 - `mcp__vantage-peers__list_memories` namespace: global, type: decision, limit: 10 Summarize any relevant prior decisions or context found. This informs the mission scope. **T2 — Classify severity** Assign a severity tier based on issue labels and body: | Tier | Criteria | |------|----------| | P0 | Production down, data loss, security breach | | P1 | Major feature broken, blocks users | | P2 | Degraded feature, workaround exists | | P3 | Minor bug, UX improvement, low impact | | P4 | Nice-to-have, future consideration | State the tier with one sentence justification. **T3 — Identify owner role** Based on labels and content, identify which VM_ROLE should own this: - `backend` / `convex` → backend role (e.g. tau) - `frontend` / `ui` → frontend role - `docs` / `documentation` → do