| name | prioritization-session |
| description | Force-rank the backlog with the user — the right framework applied, ties broken, the "not now" list made explicit, the board reordered to match. |
| disable-model-invocation | true |
Prioritization session
Turn a backlog of worthy items into one order. This is the Product Manager's prioritization operation run as a sitting: the framework does the arguing, the user does the deciding.
1. Frame
Pull the candidate set (usually Backlog + Ready, via the board skill). Pick the lightest framework that fits from the product-manager skill's prioritization.md — value/effort by default; RICE when stakeholders need numbers; CD3 when deadlines dominate — and say which and why in one line.
2. Rank
Apply the framework item by item, showing the scoring inputs so the user can veto them (a wrong Reach estimate poisons the whole RICE score). Force ranking: position 1..n, no ties — when two items argue for the same slot, ask which one the team would regret not shipping this month. Items falling below the cut line go to an explicit not-now list; closing stale ones beats deferring them forever.
3. Commit the order
Reorder the board to match (position within the Backlog column, or a Priority field if the repo uses one), and note what changed and why in one comment on the epic-index or a session summary — the next session reorders only on new information, not on mood.
Done when: every candidate item holds a unique rank or sits on the recorded not-now list, the board reflects the order, and the change note exists.
