← ClaudeAtlas

board-triagelisted

This skill should be used when the user asks to "run board triage", "triage the backlog", "prioritize the issues", "rank the unranked issues", "fill in Impact/Effort/Priority", "do the weekly triage", or wants the untriaged items on a task board classified so the prioritization/now/roadmap views become useful. It runs the export -> analyze -> apply loop: pull a snapshot, find the un-ranked/blank/stale items, rank them by the Impact x Effort rubric, and apply only the diffs. The judgment is backend-agnostic; a thin adapter does the board's I/O (kata and GitHub Projects v2 adapters ship; any board with items and fields can have one).
hsb3/dotfiles-agents · ★ 0 · Code & Development · score 73
Install: claude install-skill hsb3/dotfiles-agents
# board-triage — the prioritization pass, whatever the board runs on Turn a board full of captured-but-unranked items into a ranked, workable backlog, as a fast repeatable pass. Built on the **export → analyze → apply** loop so auth stays local, the analyst judges over a clean snapshot, and every change lands as a reviewable diff. **The judgment lives here. The I/O lives in an adapter.** Nothing on this page names a backend; everything backend-specific — how to pull a snapshot, how to write a cell, which rubric outputs the board can actually store — is in one adapter file. A new backend is a new adapter file and no edit to this page. ## When to run The weekly (or per-sprint) pass, or any time the prioritization views look thin because items carry no priority. The board is the source of truth; this keeps it honest. **Measure instead of guessing — before and after.** `scripts/board_health.py <snapshot>` runs six decay checks over the §2 snapshot: a priority band holding most of the backlog, blank bands, items with no grouping value, a grouping convention stranded in title prefixes, dead label vocabulary, and one concept split across two label spellings. Run it **before** to decide whether a pass is due (exit 0 means the board still discriminates and the pass is optional), and **after** to confirm the pass took. It checks whether a field discriminates, not merely whether it is filled — which is the failure a field-population audit reports as green, and the reason §6's defini