prioritization-advisor-re

Recommends requirements prioritization methods based on stakeholder count, requirement volume, and decision context.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill prioritization-advisor-re-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritization-advisor-re
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/prioritization-advisor-re
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill prioritization-advisor-re-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stakeholders often declare every requirement high priority, making it impossible to decide what to build first when resources are limited. This Skill guides you through adaptive questions to select and apply the right prioritization technique for your situation. ## Core Features & Use Cases - Method Selection: Answers four questions about requirement count, stakeholder group size, available data, and prioritization goal to recommend the best-fit technique. - Six Techniques Covered: In/Out sorting, three-level scales, MoSCoW, pairwise comparison, $100 allocation, and value/cost/risk spreadsheets. - Anti-Pattern Detection: Identifies pitfalls like "everything is Must-Have" and priority-by-stakeholder-power, with concrete fixes. - Use Case: A team with 35 requirements and 3 stakeholders needs to scope a release; the Skill recommends an In/Out pass followed by MoSCoW, enforcing the 60% Must-Have capacity constraint. ## Quick Start Ask the agent to help you choose a prioritization method for your requirements backlog given your stakeholder count and available data.

Frequently Asked Questions about prioritization-advisor-re

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a requirements prioritization method?▼

Answer four questions about your requirement count, stakeholder group size, available value/cost data, and prioritization goal. Small sets with one decision-maker suit three-level scales, conflicted groups suit pairwise comparison, and large sets with good data suit value/cost/risk spreadsheets.

MoSCoW vs value/cost/risk scoring for backlog prioritization?▼

MoSCoW works best for medium sets with small groups and limited data, taking 1-2 hours. Value/cost/risk scoring suits large sets with quantified benefit, penalty, cost, and risk data, requiring 4-8 hours but producing the most rigorous, auditable results.

What should I do when every requirement is marked high priority?▼

Apply a forcing constraint such as limiting Must-Have items to 60% of available capacity in MoSCoW. Alternatively use $100 allocation, where stakeholders distribute a fixed budget across requirements, making it impossible to rate everything equally high.

How do I resolve priority conflicts between stakeholders?▼

Use pairwise comparison for small sets to force direct trade-offs, or $100 allocation for groups of 3-10 to aggregate perspectives and reveal true priorities. Avoid letting the loudest or most senior stakeholder dictate rankings.

When is pairwise comparison not a good prioritization choice?▼

Pairwise comparison does not scale beyond about 20 requirements because it requires N*(N-1)/2 comparisons. For larger sets, use MoSCoW, $100 allocation, or a value/cost/risk spreadsheet instead.