What problem does it solve? Product teams often rank backlogs by gut feel, apply one framework to every decision, or produce scores that look objective but rest on guesses, which turns the roadmap into a feature factory. This Skill derives prioritization criteria from strategy, matches the framework to the context, and makes trade-offs explicit so limited resources point at the work that most advances the strategy. ## Core Features & Use Cases - Context-gated framework selection: Chooses between RICE, ICE, MoSCoW, Kano, Impact-Effort, and Eisenhower based on product stage, stakes, and reversibility instead of defaulting to one tool. - Strategy-traced scoring and sequencing: Derives weighted criteria from strategic outcomes, treats the backlog as a funnel, and sequences work by theme and dependency rather than shipping a raw ranked list. - Trade-off and communication discipline: Names Iron Triangle constraints, sets appetite instead of open-ended estimates, frames "no" with strategic context, and hands off to rigor audits. - Use Case: A PM with 40 backlog items and a fixed Q3 launch date uses this Skill to apply MoSCoW for scope negotiation, cap Must-haves at 60% of capacity, and produce a Now-Next-Later sequence with a defensible rationale for stakeholders. ## Quick Start Ask the assistant to prioritize your feature backlog using this skill, providing your product strategy, current stage, and any fixed deadlines so it can pick the right framework and sequence the work.
