prioritization-frameworks

Guides selection and application of prioritisation methods including Cost of Delay, CD3, RICE, and Kano.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill prioritization-frameworks-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritization-frameworks
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/pm-skills/prioritization-frameworks
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill prioritization-frameworks-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often sequence work by gut feel or whoever shouts loudest, leading to low-value work being done first. This Skill provides a structured reference for choosing and applying the right prioritisation method so backlogs and proposals are ordered by economic value. ## Core Features & Use Cases - Economic Sequencing: Leads with Cost of Delay and CD3 (Cost of Delay Divided by Duration) for ordering competing work in a Kanban, flow-first delivery practice. - Nine-Framework Reference: Covers Opportunity Score, ICE, RICE, Kano, MoSCoW, Eisenhower Matrix, Impact vs Effort, Risk vs Reward, and Weighted Decision Matrix with formulas and when-to-use guidance. - Use Case: A product manager with a backlog of 20 competing initiatives uses CD3 to sequence them by value lost per unit of time, then applies the Opportunity Score to identify which customer problems have high importance and low satisfaction. ## Quick Start Ask the assistant to help prioritise your current backlog using the CD3 method, providing your estimates of cost of delay and duration for each item.

Frequently Asked Questions about prioritization-frameworks

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

FAQPage Schema
How do I prioritise a product backlog using Cost of Delay?▼

Estimate the Cost of Delay for each item, meaning the value lost per unit of time it is not done, then divide by duration to get CD3. Sequence work with the highest CD3 first, which orders the queue by economic impact.

What is the difference between ICE and RICE prioritisation?▼

ICE scores ideas as Impact times Confidence times Ease for quick triage. RICE splits out Reach, calculating (Reach x Impact x Confidence) divided by Effort, giving more granularity when prioritising ideas at scale.

When should I use the Kano model versus RICE?▼

Kano is for understanding customer expectations, classifying features as must-be, performance, or attractive, and is not a ranking tool. Use RICE or CD3 when you need to rank and sequence competing work.

What is the Opportunity Score formula for prioritising customer problems?▼

Opportunity Score equals Importance multiplied by (1 minus Satisfaction), based on customer surveys normalised from 0 to 1. High importance combined with low satisfaction indicates the best opportunity to pursue.

When should I not use MoSCoW prioritisation?▼

MoSCoW sorts requirements into Must, Should, Could, and Won't categories and comes from project management rather than flow-based delivery. Use it with care for requirements scoping, but prefer CD3 when sequencing work competing for the same capacity.