# rd-triage > Rank open parents Now, Next, Later and Icebox from real signal, show the table, and write priorities only after you say yes. `rd-triage` reads the whole open backlog, ranks it from evidence rather than vibes, shows you the table, and writes nothing until you agree. Then it applies the priorities and reads one back to prove it landed. > Rank the open work in Radial, the keyboard-first issue tracker, into Now, > Next, Later and Icebox using real signal: how many issues each one blocks, > how old it is, whether anything has happened on it lately. ## When to use it Weekly, before planning, or when nobody can say what is next. Not to decide how to do something: that is `/rd-plan`. ## What it asks you One question, once: yes or no to the table it shows you. Everything before that is reading, and it tells you how many issues it read, because ranking half a backlog produces a confident, wrong answer. Its second mode steps through the triage queue instead, proposing a status, priority and label per item and applying only what you accept. ## What it writes One `radial update -p ` per row you approved, using your workspace's real priority names, followed by a `radial show --json` on one of them quoted back to you. Nothing else, and nothing outside the team you gave it. ## The signals, in order of weight How many issues it blocks is the strongest single signal, and the least flattering to anyone's intuition: an issue that blocks three others is not a "later" no matter how small it looks. Then whether it is already in progress, then age with no activity (a year-old issue nobody has touched is evidence, not an accusation), then its stated priority today, and whether it belongs to work already underway. It ranks parents. A child's priority is a detail of its parent's, and a backlog ranked at child level is a list nobody can read. ## Extension points ## A worked wrapper ```markdown --- name: support-triage description: Support-driven triage rules on top of rd-triage. extends: rd-triage --- Read rd-triage first, then apply the sections below at their hooks. ## extra-signals - An issue labelled `customer` outranks anything else of the same blocking weight; name the customer in the row's reason. - Anything labelled `sev1` is Now regardless of every other signal. ## rank-bar - Now holds at most five issues. If more qualify, re-rank and say what you cut. - Every Now row names an owner, or the row moves to Next. ## after-rank - Post the Now list to #standup as a checklist. ``` ## What it never does It never writes a priority before you say yes. It never ranks from titles alone: every row cites something it read. It never touches issues outside the team it was given, and it never closes, deletes or reassigns anything.