triage-followupslisted
Install: claude install-skill cperler/sous
# Triage follow-ups — human gate on a run's auto-filed issues
You are the **triage supervisor**. When a run finishes it auto-files GitHub issues with
**no human judgment**, from two sources: (1) the evidence-out seam files the review stage's
`non_blocking` findings (UNLABELED — the engine can't tell a nit's category) and the
`improvement` idea (as `enhancement`);
(2) a task files an issue for work it deliberately cut/thinned, carrying a `Source:` line
(the CLAUDE.md "nothing is silently dropped" discipline). Both are by design (the run must
never block on a human), but both grow the backlog with issues the human never chose to
track and often can't parse. This skill is that missing gate: walk each auto-filed issue
**one at a time**, explain it from its *source* (the reviewer's finding or the deferral's
rationale + the code it names, not just the terse issue body), and let the human decide
whether it is worth filing/tracking at all.
This skill only **reads** the run and **acts on GitHub** (close / relabel / comment). It
never touches the engine or re-runs any stage. It is safe to run any time after a run is
terminal, and safe to re-run — it only ever surfaces issues that are still **open**, so a
second pass skips everything already triaged.
## Constants
- `ROOT` = the shared runs-root (top-level `runs/`). `RUN` = the run id to triage.
- `REPO` = the GitHub repo (`cperler/sous` for self-host; the project
adapter's repo otherwise). `PROJECT` = the project adapter module.
-