Maintainer Triage Skill
An untriaged backlog isn't a to-do list — it's 400 open loops charging
interest on a volunteer's conscience. The fix isn't heroic issue-closing
weekends (they don't repeat); it's a system where every issue gets a
decision in under a minute — reproduce/needs-info/accepted/wontfix/
someday — encoded in labels, communicated by saved replies that stay human,
and maintained by a 30-minute weekly routine. Honest triage closes issues
politely that will never be done, because "open forever" is the cruelest
answer of all.
What This Skill Produces
- A label taxonomy that encodes decisions, not just topics: status
(needs-repro, needs-info, accepted, help-wanted, wontfix, someday) ×
type (bug, feature, docs, question) × effort (good-first-issue,
deep-water)
- Batch triage rules: the 30-second decision tree per issue, and the
order to eat the backlog (newest-first, oldest closed honestly in bulk)
- Saved replies for the eight recurring moments — needs-repro,
duplicate, wontfix-with-respect, stale-close, "PR welcome" (said only
when meant), the excited-first-contributor welcome
- A sustainable routine: the 30-minute weekly triage block + the
stale-policy settings, with the conscience switch: bugs never auto-stale
- The backlog burn-down plan for the existing 400
Required Inputs
Ask for (if not already provided):
- The repo: what it does, issue count, open PR count, other maintainers or
solo, current label mess
- The honest capacity: hours/week the maintainer actually has (the system
is sized to this, not to the backlog)
- The sore points: what fills the backlog (support questions? feature
wishlists? real bugs?) and what the maintainer feels worst about
- Project stance: is this a hobby, a career asset, or accidentally
load-bearing infrastructure? (wontfix courage scales with clarity here)
Framework
- Labels are decisions. Every open issue carries exactly one status
label — an issue with no status is untriaged, and the goal state is
zero untriaged. Topics are optional garnish; status is the system.
- The 30-second tree. Bug without repro → needs-repro + saved reply +
14-day clock. Repro'd bug → accepted + severity. Feature aligned with
project vision → accepted or help-wanted; not aligned → wontfix now,
kindly — parking unaligned features in "someday" is deferral disguised
as kindness, use someday only for genuinely-yes-later. Question → answer
or convert to discussion/docs issue. Duplicate → link + close.
- Eat the backlog newest-first. Newest issues have live reporters and
fresh context; the oldest 200 get the honest bulk pass: a pinned
announcement ("triage sweep this week — issues inactive >12 months close
with this message; comment to reopen") then the sweep. Reopens are
signal, not failure — that's the mechanism finding the living issues.
- Saved replies stay human. Each is 2–4 sentences, warm, and ends with
a clear next step. "PR welcome" appears only where a PR would genuinely
be reviewed and merged — as a brush-off it's the most resented phrase in
open source.
- The routine that survives. Weekly 30 minutes: new issues to zero
untriaged → needs-info clock expiries → one accepted issue advanced.
Stale-bot only on needs-info and question labels, never on accepted
bugs. The maintainer's dread is the metric: if opening the repo stops
hurting, the system is working.
Output Format
## Label taxonomy (create these)
[Status set · type set · effort set — with color/description lines]
## The 30-second tree
[Decision tree, one branch per issue shape]
## Saved replies (paste into GitHub)
[The eight, each 2-4 sentences]
## Backlog burn-down
[The pinned announcement text · sweep order · reopen handling]
## Weekly 30 minutes
[The three-step routine · stale-bot config with the bugs-never-stale rule]
Quality Checks
Anti-Patterns
Related
[[the-maintainers-no]] for the requests that need a personal no;
[[first-maintainer-month]] for new maintainers; [[email-triage-system]] —
the same discipline pointed at an inbox.
Example Trigger Phrases
- "My issues are out of control."
- "Triage my backlog."
- "Set up labels for my repo."
1---2name: maintainer-triage3description: "Get an open-source repo's issue backlog from 400-and-drowning to triaged-and-honest in one pass — a label taxonomy that encodes decisions, batch triage rules you can apply in seconds per issue, saved replies that stay kind at scale, and stale-bot policy set with a conscience. Use when a maintainer says 'my issues are out of control', 'triage my backlog', 'set up labels for my repo', or dreads opening GitHub. Produces the taxonomy, the triage pass rules, saved replies, and a sustainable weekly routine."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/maintainer-triage7---89# Maintainer Triage Skill1011An untriaged backlog isn't a to-do list — it's 400 open loops charging12interest on a volunteer's conscience. The fix isn't heroic issue-closing13weekends (they don't repeat); it's a system where every issue gets a14*decision* in under a minute — reproduce/needs-info/accepted/wontfix/15someday — encoded in labels, communicated by saved replies that stay human,16and maintained by a 30-minute weekly routine. Honest triage closes issues17politely that will never be done, because "open forever" is the cruelest18answer of all.1920## What This Skill Produces2122- A **label taxonomy** that encodes decisions, not just topics: status23 (needs-repro, needs-info, accepted, help-wanted, wontfix, someday) ×24 type (bug, feature, docs, question) × effort (good-first-issue,25 deep-water)26- **Batch triage rules**: the 30-second decision tree per issue, and the27 order to eat the backlog (newest-first, oldest closed honestly in bulk)28- **Saved replies** for the eight recurring moments — needs-repro,29 duplicate, wontfix-with-respect, stale-close, "PR welcome" (said only30 when meant), the excited-first-contributor welcome31- A **sustainable routine**: the 30-minute weekly triage block + the32 stale-policy settings, with the conscience switch: bugs never auto-stale33- The **backlog burn-down plan** for the existing 4003435## Required Inputs3637Ask for (if not already provided):38- The repo: what it does, issue count, open PR count, other maintainers or39 solo, current label mess40- The honest capacity: hours/week the maintainer actually has (the system41 is sized to this, not to the backlog)42- The sore points: what fills the backlog (support questions? feature43 wishlists? real bugs?) and what the maintainer feels worst about44- Project stance: is this a hobby, a career asset, or accidentally45 load-bearing infrastructure? (wontfix courage scales with clarity here)4647## Framework48491. **Labels are decisions.** Every open issue carries exactly one status50 label — an issue with no status is untriaged, and the goal state is51 zero untriaged. Topics are optional garnish; status is the system.522. **The 30-second tree.** Bug without repro → needs-repro + saved reply +53 14-day clock. Repro'd bug → accepted + severity. Feature aligned with54 project vision → accepted or help-wanted; not aligned → wontfix *now*,55 kindly — parking unaligned features in "someday" is deferral disguised56 as kindness, use someday only for genuinely-yes-later. Question → answer57 or convert to discussion/docs issue. Duplicate → link + close.583. **Eat the backlog newest-first.** Newest issues have live reporters and59 fresh context; the oldest 200 get the honest bulk pass: a pinned60 announcement ("triage sweep this week — issues inactive >12 months close61 with this message; comment to reopen") then the sweep. Reopens are62 *signal*, not failure — that's the mechanism finding the living issues.634. **Saved replies stay human.** Each is 2–4 sentences, warm, and ends with64 a clear next step. "PR welcome" appears only where a PR would genuinely65 be reviewed and merged — as a brush-off it's the most resented phrase in66 open source.675. **The routine that survives.** Weekly 30 minutes: new issues to zero68 untriaged → needs-info clock expiries → one accepted issue advanced.69 Stale-bot only on needs-info and question labels, never on accepted70 bugs. The maintainer's dread is the metric: if opening the repo stops71 hurting, the system is working.7273## Output Format7475```76## Label taxonomy (create these)77[Status set · type set · effort set — with color/description lines]7879## The 30-second tree80[Decision tree, one branch per issue shape]8182## Saved replies (paste into GitHub)83[The eight, each 2-4 sentences]8485## Backlog burn-down86[The pinned announcement text · sweep order · reopen handling]8788## Weekly 30 minutes89[The three-step routine · stale-bot config with the bugs-never-stale rule]90```9192## Quality Checks9394- [ ] Every issue shape in the tree ends in a decision + a saved reply —95 no branch ends in "leave it"96- [ ] Wontfix replies give the reason and thank the reporter — respect at97 scale is the whole trick98- [ ] The bulk-close announcement runs BEFORE the sweep, and reopen99 instructions are in the close message100- [ ] Stale automation exempts accepted bugs explicitly101- [ ] The routine fits the stated real hours, not the aspirational ones102103## Anti-Patterns104105- [ ] Do not build a 40-label topic museum — status labels are the system;106 taxonomy sprawl is procrastination with colors107- [ ] Do not use "someday" as a polite graveyard — unaligned features get108 an honest wontfix109- [ ] Do not auto-stale confirmed bugs; nothing burns trust faster110- [ ] Do not write saved replies that could double as form rejections —111 each names the specific next step112- [ ] Do not size the system to the backlog instead of the maintainer's113 hours114115## Related116117[[the-maintainers-no]] for the requests that need a personal no;118[[first-maintainer-month]] for new maintainers; [[email-triage-system]] —119the same discipline pointed at an inbox.120121## Example Trigger Phrases122123- "My issues are out of control."124- "Triage my backlog."125- "Set up labels for my repo."