pm-prioritize

Prioritize product opportunities from PMContext using a single scoring framework.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-prioritize-wcof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-prioritize
Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-prioritize
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-prioritize-wcof

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams turn an existing PMContext into a defensible priority order for opportunities, requirements, or backlog items. It prevents shallow feature ranking by pushing the team to prioritize underlying user problems first, trace every score back to evidence, and make tradeoffs visible.

Core Features & Use Cases

  • Framework recommendation by scenario: Chooses a single best-fit prioritization method from Opportunity Score, ICE, RICE, MoSCoW, Kano, or WSJF based on what is being ranked.
  • Evidence-based scoring: Builds a scoring table with explicit links back to PMContext so unsupported judgments are marked as assumptions instead of hidden.
  • Visual prioritization output: Produces a four-quadrant view and P0/P1/P2 ranking to support roadmap, release, and discovery decisions.
  • Use case: When a team has several customer pain points, feature ideas, or opportunity areas and needs to decide what to tackle first without mixing frameworks or relying on intuition.

Quick Start

Ask the AI to use pm-prioritize on your PMContext to rank your top opportunities and generate a traceable scoring table with a quadrant view.

Frequently Asked Questions about pm-prioritize

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

FAQPage Schema
How do I prioritize product backlog items using the RICE framework?

To prioritize a product backlog using RICE, this Skill scores items by Reach, Impact, Confidence, and Effort. It then generates a traceable scoring table with a P0/P1/P2 ranking and quadrant visualization to guide release scoping.

What is the best way to rank product opportunities instead of features?

Ranking product opportunities instead of features requires an opportunity-first approach that scores underlying user problems. This Skill evaluates customer pain points using frameworks like Opportunity Score, preventing shallow feature ranking by tracing scores back to evidence.

Can I use multiple prioritization frameworks like Kano and WSJF at the same time?

You cannot mix frameworks; this Skill applies a single best-fit prioritization method. It selects one appropriate framework, such as Kano or WSJF, based on your specific scenario to ensure consistent scoring and clear tradeoff visualization.

How do I trace prioritization scores back to evidence for roadmap planning?

Tracing prioritization scores back to evidence requires linking each score to PMContext. This Skill builds a scoring table with explicit evidence links, marking unsupported judgments as assumptions to ensure roadmap planning relies on validated data.

Does backlog prioritization work without existing PMContext evidence?

Backlog prioritization here requires PMContext-based evidence to function correctly. Without it, the Skill cannot trace scores to validated data and will explicitly mark any unsupported scoring judgments as assumptions rather than facts.

How do I visualize product strategy tradeoffs during discovery?

Visualizing product strategy tradeoffs during discovery is done using a four-quadrant view. This Skill outputs a quadrant chart alongside P0/P1/P2 classification to make opportunity assessment and prioritization tradeoffs immediately visible for planning.