prioritization-advisor

Overview of prioritization-advisor skill

prioritization-advisor helps product teams choose a prioritization framework that fits the decision, not just the trend. It is best for product managers, founders, and ops leads who need a practical answer to “Should we use RICE, ICE, value/effort, or something else?” and want guidance that reflects stage, team maturity, data quality, and stakeholder pressure.

The real job-to-be-done is reducing framework churn and debate. Instead of forcing one scoring model everywhere, the prioritization-advisor skill recommends a framework that matches how your team actually makes decisions, then explains how to apply it without overengineering the process.

When prioritization-advisor is the right fit

Use this skill when you need a decision support answer for roadmap planning, intake triage, or cross-functional prioritization. It is especially useful when your team keeps switching methods, your metrics are partial, or the choice between speed and rigor is not obvious.

What makes prioritization-advisor different

This skill is interactive and context-sensitive, so it is not just a static framework comparison. The prioritization-advisor skill asks for the conditions that matter most and then adapts the recommendation, which makes it more useful than a generic prioritization prompt.

What users usually want from it

Most users want three things: a framework recommendation, a quick rationale they can share with others, and enough implementation guidance to start using it immediately. prioritization-advisor for Decision Support is designed to give you all three in one pass.

How to Use prioritization-advisor skill

Install prioritization-advisor in your skill library

Use the directory install flow for the repo, for example: npx skills add deanpeters/Product-Manager-Skills --skill prioritization-advisor. If your environment uses a different skills manager, install the skill into the same place you keep other reusable workflow skills so it can be invoked consistently.

Feed it the right decision context

The prioritization-advisor usage works best when you provide a clear but compact brief: product stage, team size, whether you have reliable data, how often priorities change, who the decision is for, and what kind of work is being ranked. A strong prompt looks like this:

“Recommend a prioritization approach for a seed-stage B2B SaaS team with limited usage data, one PM, two engineers, and a founder who wants fast weekly decisions. We need to compare growth experiments, support fixes, and one strategic integration.”

That input is better than “Which framework should we use?” because it gives the skill the constraints that determine the right tradeoff.

Read these files first

Start with SKILL.md, then inspect any linked sections inside it before assuming the workflow is generic. In this repo, there are no supporting folders such as rules/, resources/, or references/, so the main value is in understanding the main skill file deeply and using its prompts and examples as the source of truth.

Use the output as a decision aid, not a policy

The prioritization-advisor guide is most useful when you treat the recommendation as a decision support draft. If the suggested framework conflicts with your operating rhythm, keep the reasoning and adapt the method instead of copying the workflow mechanically. This matters most when you have stakeholder politics, sparse data, or mixed work types in one backlog.

prioritization-advisor skill FAQ

Is prioritization-advisor only for product managers?

No. It is strongest for product management, but it also helps founders, design leads, and operations teams that need a defendable way to rank competing work. If your team must make tradeoffs under uncertainty, the prioritization-advisor skill can still help.

How is this different from a normal prompt?

A normal prompt usually asks for one framework in isolation. prioritization-advisor is better when the choice depends on context, because it can weigh stage, decision frequency, and data quality before recommending a method. That usually produces less generic advice and fewer misfit recommendations.

Is it beginner-friendly?

Yes, as long as you can describe your team and your backlog in plain language. You do not need a mature analytics stack to use it, but you do need to share enough context for the skill to distinguish between strategic bets, incremental improvements, and urgent operational work.

When should I not use it?

Do not use prioritization-advisor if you already have a mandated company framework and only need a fill-in-the-blank template. It is also a poor fit when the real problem is not prioritization method selection but unclear strategy, missing goals, or unresolved ownership.

How to Improve prioritization-advisor skill

Give sharper inputs on decision reality

The best results come from describing the actual decision environment, not just the problem category. Include what is being prioritized, how often decisions happen, whether you need speed or auditability, and who must buy into the outcome. Those details let prioritization-advisor choose a framework that matches the real workflow.

Ask for the implementation shape you need

If you want more than a recommendation, say so. For example: “Recommend a framework and show how to score 5 backlog items,” or “Suggest a lightweight version we can use in weekly planning.” That improves prioritization-advisor usage because the output can be tailored to adoption, not only selection.

Watch for common failure modes

The biggest failure mode is overloading the skill with vague goals like “make prioritization better.” Another is giving a framework preference before giving context, which can bias the result toward the wrong model. If you are seeing friction, clarify whether the issue is decision speed, stakeholder alignment, or evidence quality.

Iterate after the first recommendation

Treat the first answer as a starting recommendation and refine with one follow-up question: “What would change if we had more data?”, “How would this work for mixed strategic and support work?”, or “What if the founder wants final say?” That second pass usually yields a more usable prioritization-advisor skill outcome than trying to perfect the initial prompt.