skills.rest
SpaceZephyr
SpaceZephyrCOMMUNITY
Explore all skills by this author →
GitHub

SPACE-prioritization-engine

Rank product demands using RICE, ICE, Kano, and cost-benefit models.

14|4|Updated Mar 31, 2026
Search Tags:#resource allocation#product roadmap#rice scoring#feature ranking#ice scoring#kano analysis#demand prioritization
One-click install
npx skills add https://github.com/SpaceZephyr/allSkills --skill space-prioritization-engine-spacezephyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SPACE-prioritization-engine
Source: https://github.com/SpaceZephyr/allSkills/tree/main/pm-prioritization-engine
Command: npx skills add https://github.com/SpaceZephyr/allSkills --skill space-prioritization-engine-spacezephyr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams frequently face subjective, unaccountable demand prioritization that leads to wasted engineering resources, missed business targets, and persistent stakeholder conflicts over what to build next. This skill eliminates guesswork by providing a structured, multi-model scoring framework that produces transparent, defensible prioritization decisions.

Core Features & Use Cases

  • Multi-model scoring support: Evaluate demands using RICE, ICE, Kano, and cost-benefit analysis models, with automatic discrepancy marking between model results to surface conflicting priorities for team discussion.
  • Calibrated roadmap generation: Output versioned roadmap plans (Now/Next/Later) aligned with team resource constraints, business goals, and hard deadlines, plus actionable recommendations for cutting low-value or harmful demands.
  • Use case example: A product team with 15 competing feature requests and 3 available engineers for a 6-week cycle can use this skill to objectively rank demands, align stakeholders on a Q3 growth-focused roadmap, and clearly explain why certain features were prioritized or deferred.

Quick Start

Use the SPACE-prioritization-engine skill to rank the 12 feature requests collected from customer feedback last month, with 3 engineers available for the next 6 weeks and a Q3 target of 15% new user activation.

Frequently Asked Questions about SPACE-prioritization-engine

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

FAQPage Schema
How do I objectively rank competing feature requests when engineering resources are constrained?▼

Feature request ranking uses multi-model scoring frameworks like RICE, ICE, and Kano to evaluate competing demands objectively. This eliminates subjective guesswork by providing transparent, defensible prioritization decisions that align stakeholders on what to build next under constrained resources.

What is the difference between RICE and ICE scoring for product roadmap prioritization?▼

RICE scoring evaluates reach, impact, confidence, and effort, while ICE scoring uses impact, confidence, and ease. Applying both models simultaneously surfaces cross-model discrepancies, highlighting conflicting demand priorities for team discussion during product roadmap prioritization.

How do I generate a calibrated product roadmap aligned with business goals and hard deadlines?▼

Calibrated roadmap generation ranks demands using cost-benefit analysis and scoring models against team resource constraints and business targets. This outputs a versioned Now/Next/Later roadmap plan with actionable recommendations for cutting low-value or harmful demands to meet hard deadlines.

Does Kano analysis work for resolving cross-stakeholder conflicts over demand prioritization?▼

Kano analysis works for resolving cross-stakeholder conflicts by categorizing demands based on customer satisfaction and functionality. It provides structured, explainable scoring that helps product teams transparently justify why certain features are prioritized or deferred during stakeholder review sessions.

When should I use cost-benefit analysis instead of RICE scoring for feature ranking?▼

Cost-benefit analysis should be used instead of RICE scoring when comparing financial ROI directly against implementation costs. Running both models simultaneously is recommended, as built-in cross-model discrepancy detection marks conflicting feature ranking results for immediate team discussion.

Related Skills

Explore More Product & Management Skills→
neurofooneurofoo
106

moscow

Categorize project requirements into Must have, Should have, Could have, and Won't have.

Community
Basic
RebelHawk-TKRebelHawk-TK

roadmap-planning

Convert strategy into a sequenced, outcome-driven roadmap with prioritized backlog and dependency map.

Community
Advanced
adriaanmostert1976-labadriaanmostert1976-lab

prioritization

Prioritize initiatives by strategic impact and operational capacity using a two-dimensional scoring model.

Community
Advanced
MatrixFounderMatrixFounder
4

skill-product-backlog-prioritization

Calculate WSJF scores for product backlog items using a Python script.

Community
Intermediate