backlog-triage
FeaturedTurn 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.
Install
Quality Score: 93/100
Skill Content
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
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.
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.
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.