← ClaudeAtlas

backlog-triagelisted

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.
rampstackco/claude-skills-pm · ★ 4 · AI & Automation · score 83
Install: claude install-skill rampstackco/claude-skills-pm
# 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