dragoon0x/everything-design-taste

feature-prioritization

Feature prioritization frameworks, scoring models, roadmap design, and saying no to features.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill feature-prioritization

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,234 B
  • docs SUMMARY.md 123 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Feature Prioritization

Frameworks

RICE Score

  • Reach: How many users affected per quarter?
  • Impact: How much will it move the needle? (3=massive, 2=high, 1=medium, 0.5=low)
  • Confidence: How sure are we? (100%, 80%, 50%)
  • Effort: Person-months to build
  • Score = (Reach × Impact × Confidence) / Effort

Impact vs Effort Matrix

           Low Effort    High Effort
High       Quick Wins     Big Bets
Impact     (do first)     (plan carefully)

Low        Fill-ins       Avoid
Impact     (if time)      (time sinks)

MoSCoW

  • Must have: Product doesn't work without it
  • Should have: Important but not critical
  • Could have: Nice but can live without
  • Won't have: Explicitly out of scope (this matters)

Saying No

  • 'Not now' is better than 'no' (less confrontational)
  • Explain the tradeoff: 'If we build X, we delay Y by 3 weeks'
  • Ask: 'What would you cut to make room for this?'
  • Document the decision and reasoning (prevents re-litigation)