triagelisted

# /triage — Insights Triage Reads Claude Code `/insights` output (report + facets + session-meta), analyzes each section systematically, and creates GitHub issues across repos with confirmation at every step. ## Mode **Plan mode with interactive confirmation.** Enter plan mode (`EnterPlanMode`) before starting. Phases 1-3 are automated data gathering. Phases 4-5 are interactive — the agent proposes, the user confirms. No issues are created without explicit approval. **Model:** Use Opus for analysis (heavy-tier reasoning). The cross-referencing and issue-grouping logic benefits from maximum capability. ## Prerequisites - `/insights` has been run (`~/.claude/usage-data/report.html` exists) - `gh` CLI is authenticated (`gh auth status`) - Repos referenced in session-meta have git remotes ## Invocation ``` /pds:triage # Full triage of latest insights /pds:triage --section friction # Triage only the friction section /pds:triage --repo <name> # Triage for one repo only /pds:triage --dry-run # Analyze and propose but don't create issues ``` ## Protocol ### Phase 1: Load 1. Verify insights data exists: ```bash test -f ~/.claude/usage-data/report.html && echo "report found" || echo "MISSING — run /insights first" ls ~/.claude/usage-data/facets/*.json 2>/dev/null | wc -l ls ~/.claude/usage-data/session-meta/*.json 2>/dev/null | wc -l ``` If report is missing, abort: "Run `/insights` first to generate the report."