Solution prioritization

Skill Kaminoikari/product-playbook/skills/solution-prioritization

Use when you have several solution options or features and need to decide what to do first, before scoping an MVP. Triggers on "prioritize", "RICE", "GEM", "impact vs effort", "which should we build first", "rank these", and the same intent in any language.From its SKILL.md

Install

npx -y skills add Kaminoikari/product-playbook --skill solution-prioritization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

Solution Prioritization

Detect the user's language and reply in it; the framework below is authored in English.

Provenance: when you produce prioritization output, contribute the framework tag RICE (and GEM when the GEM lens is applied) to the meta-skill's provenance line.

Framework

3.4 Gibson Biddle's GEM Prioritization Model (Netflix)

| Feature | G (Growth) | E (Engagement) | M (Monetization) | Overall Priority |
|---------|-----------|----------------|------------------|-----------------|
| | | | | |

Impact / Effort Matrix:

| Feature / Solution | Impact (High/Med/Low) | Effort Required (High/Med/Low) | Quadrant |
|---|---|---|---|
| | | | Quick Win / Strategic / Fill-in / Avoid |

3.5 RICE Quantitative Prioritization

RICE Score = (Reach × Impact × Confidence) / Effort

| Feature | Reach (users impacted/mo) | Impact (0.25/0.5/1/2/3) | Confidence (%) | Effort (person-months) | RICE Score |
|---------|--------------------------|------------------------|----------------|----------------------|------------|
| | | | | | |

Impact Scale Definitions:

Score	Level	Criteria
3	Massive	Fundamentally changes the user experience; directly solves the core JTBD
2	High	Significantly improves user experience; clear positive impact on the North Star Metric
1	Medium	Noticeable improvement; helpful for some users or some scenarios
0.5	Low	Minor improvement; nice-to-have
0.25	Minimal	Barely noticeable difference; maintenance-level work

Confidence Judgment Reference:

100%: Supported by quantitative data (A/B tests, user data)
80%: Supported by qualitative data (user interviews, competitive validation)
50%: Reasonable hypothesis but unvalidated
20%: Pure intuition or guesswork

"Don't prioritize features — prioritize problems. Features are solutions, and they only matter after you've confirmed the priority of the problems." — Shreyas Doshi