- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add rampstackco/claude-skills --skill backlog-triage -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add rampstackco/claude-skills --skill backlog-triage -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add rampstackco/claude-skills --skill backlog-triage -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add rampstackco/claude-skills --skill backlog-triage -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/rampstackco/claude-skills/tree/HEAD/dist/codex/.agents/skills/backlog-triageDe l'éditeur
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.
ticket-authoring)roadmap-planning)discovery-research-synthesis)user-feedback-aggregation)sprint-operations)test-case-authoring)If an item has no source or no reporter, ask before scoring it. A score built on an anonymous one-liner is a guess with a number on it.
Triage is a filter, not a sort. Most raw items should not reach the top of the queue. The ones that do must be ready to pull.
Requests arrive from support, sales, customers, monitoring, incident reviews, internal teams, and feedback programs. Every one gets an intake record before it enters the backlog:
Nothing enters the backlog without an intake record. A hallway ask becomes a record or it stays a hallway ask.
Duplicates hide demand. Five tickets with one reporter each look like five small problems. One ticket with five reporters is a signal.
Find duplicates three ways:
To merge: keep the oldest item as the primary. Link the rest to it and close them as duplicates. Add their reporters to the primary. Update the reporter count field.
Reporter count is a field, not a vibe. "Lots of people want this" is not an input. "11 reporters, 3 paying accounts" is.
Assign one of the five types from ticket-authoring: bug, task, story, spike, or epic. A defect is a bug. A user outcome is a story. An open question is a spike. A group of outcomes toward one metric is an epic.
If you cannot classify it, the item is not ready. Send a question back to the reporter. Do not guess the type and write a ticket around the guess.
Score inputs, not conclusions. Every score is written with the inputs that produced it, so anyone can re-derive it next month.
Bugs: severity and frequency as separate fields.
Severity uses the scale in the ticket-authoring bug template. Frequency comes from reporter count, error logs, or analytics, never from the loudest reporter's estimate.
Stories and epics: value against effort, inputs on the record. Use the model your team already trusts. If you have none, RICE is one option: reach, impact, confidence, effort. Record each input with its source. Another team might use value, urgency, and effort. The model matters less than writing the inputs down. See references/scoring-template.md.
Tasks and spikes inherit priority from the story or decision they unblock.
Every item leaves triage in one of three states.
ticket-authoring; do not keep a second copy.The backlog is a queue, not an archive.
See references/aging-policy-guide.md.
The runbook is references/triage-checklist.md.
ticket-authoring for any fields still missing.user-feedback-aggregation.Return a triage summary in markdown:
Name files triage-[yyyy-mm-dd].md when saving to disk.
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
For triage, that means: an item missing reach, frequency, or effort is ranked as "unscored" with the missing input named, not given a plausible number.
references/intake-template.md - The minimum intake record and the question-back message. Read when an item arrives without one.references/triage-checklist.md - The weekly session runbook, minute by minute. Read before running a session.references/scoring-template.md - The severity and frequency grid for bugs and a value and effort sheet with inputs. Read when scoring anything.references/aging-policy-guide.md - How to set the decay threshold and ceiling, and what to do when the backlog is over it. Read when the backlog feels unreadable.references/example-triage-session.md - Ten raw items in, a ranked list out, with two merges, one park, and one decline. Read to calibrate the level of detail.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 re
---name: backlog-triagedescription: Turn an inbox of raw requests (bug reports, feature asks, support escalations, feedback, incident follow-ups)…---# dist/codex/.agents/skills/backlog-triage/SKILL.mdVue d'ensemble
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.
FAQ
Téléchargez dist/codex/.agents/skills/backlog-triage/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/rampstackco/claude-skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.