backlog-triage

Featured

Turn an inbox of raw requests (bug reports, feature asks, support escalations, feedback, incident follow-ups) into a ranked, deduplicated backlog where every item at the top meets the definition of ready, with recorded scores, merge links, and a written reason for every park and decline. Use this skill whenever the user wants to triage incoming work, groom or prune a backlog, merge duplicate tickets, score or rank requests, decide what the team works on next, or run a weekly triage session. Triggers on triage, groom the backlog, backlog grooming, prioritize the backlog, dedupe tickets, duplicate tickets, what should we work on next, inbox of bugs, feature requests pile, rank these, is this ready, backlog is too big, stale tickets, severity vs frequency. Also triggers when the user pastes a list of raw requests or bug reports and asks what to do with them, even if they never say the word triage.

AI & Automation 1,090 stars 148 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Backlog Triage Turn a pile of raw requests into a short, ranked queue where everything at the top can be pulled today. Tracker-agnostic: works in Jira, Linear, GitHub Issues, or your tracker of choice. --- ## When to use - A pile of bug reports, feature asks, and escalations has no order - The same complaint shows up as five tickets from five people - The team asks "what should we work on next?" and nobody can answer from the backlog - Running the weekly triage session - The backlog has grown past the point anyone reads it - Checking whether the top of the queue is actually ready to pull ## When NOT to use - Writing the ticket itself, fields and all (use `ticket-authoring`) - Sequencing initiatives across quarters (use `roadmap-planning`) - Synthesizing a batch of research interviews (use `discovery-research-synthesis`) - Aggregating feedback channels into themes (use `user-feedback-aggregation`) - Running sprint planning, standups, or retros (use `sprint-operations`) - Writing the test plan for one item already in the queue (use `test-case-authoring`) --- ## Required inputs - The raw items: pasted text, an export, or a tracker query - The current backlog, if one exists, to dedupe against - The scoring model the team uses, or agreement to use the defaults here - The backlog ceiling and aging threshold, or agreement to set them now - Who can answer questions about each item (reporter or owner) If an item has no source or no reporter, ask before scoring it. A score ...

Details

Author
rampstackco
Repository
rampstackco/claude-skills
Created
6 months ago
Last Updated
2 days ago
Language
JavaScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

backlog-triage

Turn an inbox of raw requests (bug reports, feature asks, support escalations, feedback, incident follow-ups) into a ranked, deduplicated backlog where every item at the top meets the definition of ready, with recorded scores, merge links, and a written reason for every park and decline. Use this skill whenever the user wants to triage incoming work, groom or prune a backlog, merge duplicate tickets, score or rank requests, decide what the team works on next, or run a weekly triage session. Triggers on triage, groom the backlog, backlog grooming, prioritize the backlog, dedupe tickets, duplicate tickets, what should we work on next, inbox of bugs, feature requests pile, rank these, is this ready, backlog is too big, stale tickets, severity vs frequency. Also triggers when the user pastes a list of raw requests or bug reports and asks what to do with them, even if they never say the word triage.

4 Updated 2 days ago
rampstackco
AI & Automation Listed

batch-triage

Triage an inherited backlog in one pass — many existing issues at once, rather than one new item at a time. Classifies each by reading its own content and the code it names, dedupes, marks the stale, and produces tracker tickets with labels and blocking edges. Invoke by name when adopting a repo that arrives with a backlog.

4 Updated 2 days ago
thientranhung
AI & Automation Listed

cx-backlog-triage

Use to analyse a support backlog and find the conversations actually at risk — never-touched tickets, work stalled on your side, customers stranded with a bot, and unassigned open work. Trigger for "report on our open tickets", "daily outstanding tickets report", "how many tickets have we not responded to", "find tickets waiting on us", "customers stuck with a bot and no human", aging backlog, or a backlog that keeps growing.

1 Updated 3 months ago
rulebase-co