Dec prioritization frameworks
Skill jpoindexter/design-engineering-canon/skills/dec-prioritization-frameworks
Prioritization frameworks — RICE, Kano model, MoSCoW, Value vs Effort 2×2. Use when ranking a backlog, deciding what ships in v0 vs later, defending a sequencing decision, or classifying features as basics vs delighters.From its SKILL.md
npx -y skills add jpoindexter/design-engineering-canon --skill dec-prioritization-frameworksAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
1.4 KB, 291 tokens by cl100k_base, as published. Nobody here has run it
Prioritization Frameworks
Defensible ways to order a backlog and decide what's in vs out.
- RICE: (Reach × Impact × Confidence) ÷ Effort. A single comparable priority score; forces you to estimate each factor.
- Kano Model: Features map to Basic (expected — absence angers), Performance (linear satisfaction), and Delighters (exciters — unexpected joy). Delighters decay into Basics over time, so keep finding new ones.
- MoSCoW: Must / Should / Could / Won't have. Fast, coarse, good for scoping a release with stakeholders.
- Value vs Effort (2×2): Quick wins (high value / low effort) vs big bets vs time-sinks vs fill-ins. The fastest visual triage.
How to apply
- Use Value vs Effort for a 5-minute triage; promote RICE when you need a defensible number.
- Kano answers a different question — not "what first" but "what kind": ship all Basics, pick a few Performance levers, add one Delighter.
- MoSCoW "Won't" is the most valuable column — it makes cuts explicit. Park, don't delete.
- Quick wins first to build momentum; sequence one big bet behind them.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.