feedback-triagelisted

Triage a tool's accumulated dogfooding feedback reports into a leverage-ordered improvement backlog — reconcile what already shipped, cluster findings by underlying cause rather than symptom, assign each cluster a disposition (attack this tool, route out to the tool that owns it, or decline), apply a promotion gate (reinforced across reports, specific, actionable), and emit a triage document with a status-tracked promotion table. Use on "triage the feedback backlog", "cluster the feedback reports", "what should this tool fix next", "promote the recurring feedback", or "/feedback-triage". Explicitly invoked maintenance — never run proactively; it reads a whole corpus. If the tool's binding registers its own triage template (e.g. keel's reflection-triage), follow that template. Not for consolidating journal entries into guidance (that is consolidate-knowledge), not for a corpus of one report with no prior triage (nothing to cluster yet — a 1-report delta over an existing baseline IS a valid later pass), not for
grimaldost/craft-collection · ★ 2 · AI & Automation · score 71

Install: claude install-skill grimaldost/craft-collection

# Feedback Triage The downstream half of the tool-feedback loop. `tool-feedback` captures one report per session; this pass reads the accumulated corpus and turns it into the tool's improvement backlog. Capture is tuned for recall; triage is tuned for precision — the bar is *a maintainer can pick the top item and build it without re-reading the reports*. It ends at the backlog document: building promotions, version bumps, and CHANGELOGs belong to the tool's release process. ## The pipeline — run in order 1. **Scope.** Resolve the tool from the `feedback-targets` table in loaded context (ask once if absent; never hunt). Rebuild the dir's `INDEX.md` first (run `uv run --no-project python "${CLAUDE_PLUGIN_ROOT}/skills/feedback-triage/scripts/build_feedback_index.py" <dir>`): its `### Untriaged` section is the input list — reports in no triage doc's **Inputs**, detection by input lists, not dates — and the `extends`-lookup in steps 2–3 is one Read. A triage doc is detected by its `# Triage` H1, never its filename (`references/mechanics.md`). State the count: `N un-triaged reports`. N of 1 with no prior triage doc is too thin — stop with a note (nothing to cluster); 1 new report over an existing baseline is a valid delta pass (step 7). When the invocation names a different count or set, the directory is authoritative — note the discrepancy under **Inputs**. Note any triage doc already dated today and re-check at emit (step 7). 2. **Reconcile