prioritization-frameworks
by phurynReference guide for the prioritization-frameworks skill: 9 prioritization methods with formulas, when-to-use guidance, and templates. Useful for Product Management when comparing RICE, ICE, Kano, MoSCoW, Opportunity Score, and similar approaches to rank problems, ideas, or initiatives.
This skill scores 74/100, which means it is a solid but limited directory candidate: it gives users enough framework guidance and formulas to be worth installing, but it is more of a reference/selection aid than a fully operational, agent-driven workflow. For directory users, that means it should be helpful when choosing among prioritization methods, though they should expect to do some interpretation and adaptation.
- Explicit trigger guidance covers choosing a prioritization method, comparing frameworks like RICE vs ICE, and learning how they work.
- Substantive reference content includes formulas and when-to-use guidance, especially for Opportunity Score and ICE.
- No placeholder markers or experimental/demo signals; the SKILL.md appears to contain real instructional content.
- Supporting assets are absent (no scripts, references, resources, or examples), so execution will rely mainly on the text in SKILL.md.
- Operational coverage looks broader than deep: it is a framework reference, but not a step-by-step decision workflow for all listed methods.
Overview of prioritization-frameworks skill
The prioritization-frameworks skill helps you choose and apply a prioritization method instead of improvising one. It is most useful for Product Management work where you need to compare problems, ideas, or initiatives and explain why one rises above another. The core value is practical decision support: converting messy input into a framework-backed ranking with formulas, tradeoffs, and “when to use” guidance.
What this prioritization-frameworks skill is for
Use the prioritization-frameworks skill when you need a fast way to decide between frameworks like RICE, ICE, Kano, MoSCoW, or Opportunity Score. It is a fit if you want the skill to help you frame the decision, not just list methods.
Best-fit users and jobs to be done
This prioritization-frameworks guide is strongest for PMs, founders, product ops, and analysts who need a defensible way to rank work. It is especially relevant when stakeholders disagree, when “importance” and “effort” are both in play, or when you need to prioritize problems instead of feature requests.
What differentiates it
The repo centers on a clear principle: prioritize problems, not solutions. That matters because many generic prompts jump straight to feature sorting. The prioritization-frameworks skill is more useful when you need a framework that creates a reasoned shortlist and helps you explain the logic behind the ranking.
How to Use prioritization-frameworks skill
Install the skill
Install with npx skills add phuryn/pm-skills --skill prioritization-frameworks. That is the prioritization-frameworks install path for agents and local workflows that support skills from this repo.
Give the skill decision-ready input
The prioritization-frameworks usage pattern works best when you provide a small set of comparable items plus the decision context. For example: user problems, candidate initiatives, expected reach, known constraints, and what “success” means. A weak prompt says “prioritize my backlog.” A stronger prompt says “prioritize these 8 problems for a B2B SaaS onboarding team using a framework that accounts for customer pain, confidence, and implementation effort.”
Read the repo in the right order
Start with SKILL.md first because it contains the framework logic and the source-of-truth guidance. If you are exploring how the skill is organized, inspect README.md, AGENTS.md, metadata.json, and any rules/, resources/, references/, or scripts/ folders. For this repo, SKILL.md is the only file, so the main installation question is whether the framework logic fits your use case.
Turn a rough request into a useful prompt
A good prioritization-frameworks prompt includes: the decision type, the list of candidates, the user or business context, and the constraints that matter. Example shape: “Use a prioritization framework to rank these 6 customer problems for a mobile banking app. Optimize for customer impact, feasibility this quarter, and clarity of explanation to stakeholders. Show the formula or scoring logic you used.”
prioritization-frameworks skill FAQ
Is prioritization-frameworks only for Product Management?
No, but prioritization-frameworks for Product Management is the clearest fit. It also works for roadmap planning, operations, and any situation where you need structured tradeoffs. If you are only picking between two simple tasks, a full framework may be overkill.
How is this different from a normal prompt?
A normal prompt may produce a ranking with no consistent logic. The prioritization-frameworks skill gives you an explicit method, which makes the result easier to audit, defend, and reuse across teams.
Do I need to know the frameworks before installing?
No. The skill is useful as a guided reference if you want to learn the methods while using them. That said, it works best when you can provide real input data rather than vague ideas.
When should I not use this skill?
Skip it if your decision depends mainly on hard constraints that make ranking irrelevant, or if you need deep statistical modeling rather than a lightweight prioritization rubric. It is also a poor fit if the items are not comparable.
How to Improve prioritization-frameworks skill
Provide inputs the framework can actually score
The best outputs come from concrete, comparable items. Instead of “improve onboarding,” provide distinct problems such as “users fail at account linking,” “users drop at KYC upload,” and “users do not understand next steps.” The prioritization-frameworks skill can only rank what it can clearly differentiate.
State the tradeoff you want optimized
If you care most about customer pain, say so. If you care most about speed, revenue, or confidence, say that too. This matters because different frameworks emphasize different dimensions, and the best prioritization-frameworks usage depends on the decision goal.
Ask for the scoring logic, not just the rank
Request the rationale, formula, and assumptions behind the order. That helps you catch hidden bias, challenge bad inputs, and adapt the method to your own team. For example: “Rank these items, show the criteria used, and explain why the top 3 beat the rest.”
Iterate with missing-data checks
If the first pass feels uncertain, ask the skill to flag unknowns and show what extra evidence would change the ranking. That is usually more valuable than forcing false precision, especially in early Product Management discovery work.