From pm-planning
Applies RICE, MoSCoW, Kano, ICE, Opportunity Scoring frameworks to rank features and backlog items. Use for prioritizing what to build next, backlog grooming, or tradeoff evaluation.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-planningThis skill uses the workspace's default tool permissions.
Apply the right prioritisation framework to any backlog and produce a clear, defensible ranking with rationale — not just a sorted list.
Apply RICE, ICE, MoSCoW, Kano, and Value vs Effort frameworks for prioritizing features, roadmaps, backlogs, and trade-offs.
Scores and ranks product backlogs using RICE, WSJF, ICE, MoSCoW frameworks. Use for prioritizing features, roadmap decisions, and evaluating trade-offs.
Scores and prioritizes feature lists or initiatives using RICE, ICE, or custom frameworks. Outputs ranked tables with scores, rationales, cut lines, and capacity recommendations.
Share bugs, ideas, or general feedback.
Apply the right prioritisation framework to any backlog and produce a clear, defensible ranking with rationale — not just a sorted list.
Ask the user which framework they prefer, or recommend based on context:
| Situation | Recommended Framework |
|---|---|
| Need a quick, data-driven score | RICE |
| Stakeholder alignment meeting | MoSCoW |
| Understanding customer delight vs expectations | Kano |
| Early-stage startup, fast decisions | ICE |
| Identifying underserved customer needs | Opportunity Scoring |
| Strategic portfolio decisions | Value vs Effort Matrix |
Formula: (Reach × Impact × Confidence) ÷ Effort
| Factor | Definition | Scale |
|---|---|---|
| Reach | Users impacted per quarter | Actual number |
| Impact | Effect on goal per user | 0.25 / 0.5 / 1 / 2 / 3 |
| Confidence | How certain are you? | 50% / 80% / 100% |
| Effort | Person-months required | Actual number |
Output table:
| Feature | Reach | Impact | Confidence | Effort | RICE Score | Priority |
|---|
Categorise each feature as:
Always ask: "Must have for what?" — define the scope (launch, sprint, quarter) before categorising.
Formula: Impact + Confidence + Ease (each 1–10)
Quick, subjective — good for early decisions before data exists.
Classify features into:
Recommend building: all Basic features first → Performance features for key use cases → 1–2 Excitement features per release.
Framework Used: [RICE / MoSCoW / ICE / Kano / Custom] Scope: [Sprint / Quarter / Release] Goal being prioritised against: [Metric or objective]
[Scored table using selected framework]
Recommended Build Order:
Explicitly Deprioritised:
Assumptions Made: