CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prioritization-frameworks

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-organized reference with precise formulas, explicit scales, and clear framework-selection guidance, held back mainly by an implicit rather than explicit application workflow and minor re-statements of frameworks Claude already knows. Structure and navigation are good, with clearly signaled external resources.

Suggestions

Add a short numbered workflow for the recommended path (e.g., 1. Survey customers on Importance/Satisfaction, 2. Normalize to 0–1, 3. Compute Opportunity Score, 4. Plot and prioritize the upper-left quadrant) so the application sequence is explicit rather than scattered across prose.

Include a small worked example for Opportunity Score (sample survey responses → normalized values → computed score → prioritized pick) to make the guidance fully executable end-to-end.

Trim table rows that restate standard knowledge Claude already has (Eisenhower, MoSCoW category names, Kano's five categories) down to just the non-obvious guidance — when to use each and its known pitfalls.

DimensionReasoningScore

Conciseness

The body is compact and token-efficient: formulas are stated inline, the 9-framework overview uses a dense table, and there is no padded prose. Minor over-explanation of concepts Claude already knows keeps it below anchor 5 — e.g., 'Eisenhower Matrix | Urgent vs Important', 'MoSCoW | Must/Should/Could/Won't', and the Kano category list are standard knowledge, though each is only a single table row.

4 / 5

Actionability

Formulas are concrete and executable with explicit scales — 'Opportunity Score = Importance × (1 − Satisfaction)', 'C (Confidence) = 0-100%', 'E (Effort) = person-months', 'normalize to 0–1 scale' — plus linked templates and a selection table with recommendations. It falls short of anchor 5 because there is no worked example (e.g., a sample survey-to-score calculation) and some inputs are unspecified (survey sample, how to estimate Confidence).

4 / 5

Workflow Clarity

The recommended path is present but implicit: 'Survey customers on Importance and Satisfaction for each need (normalize to 0–1 scale)' → compute → 'Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot', yet no explicit numbered sequence or checkpoints (e.g., how many customers, how to handle ties, when to switch frameworks). Anchor 4's 'clear sequence' is not met since application steps are scattered across prose rather than laid out; there are no destructive/batch operations so no cap applies.

3 / 5

Progressive Disclosure

Good structure with clear sections, a comparison table, and clearly labeled one-level-deep external links (Templates, Further Reading); no bundle files exist so nothing is buried or nested. It misses anchor 5 because at ~77 lines all framework details are inlined — the under-50-line simple-skill exception doesn't apply — and per-framework detail could arguably live in reference files with SKILL.md as a pure overview/decision table.

4 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit and concrete 'what' and 'when' clauses, good natural trigger terms, and named frameworks that make it largely distinguishable from other skills. The main improvement opportunities are verb-driven capability statements and a few more natural trigger synonyms.

DimensionReasoningScore

Specificity

The description names the domain ('prioritization frameworks') and lists several concrete components — 'formulas, when-to-use guidance, and templates' — plus six named frameworks (RICE, ICE, Kano, MoSCoW, Opportunity Score). It falls short of anchor 5 because the framing is noun-driven ('Reference guide to...') rather than enumerating multiple concrete actions, though it clearly exceeds anchor 3's '1-2 concrete actions' with its comprehensive component list.

4 / 5

Completeness

Explicitly answers both questions: the 'what' is concrete ('Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates') and the 'when' is an explicit 'Use when...' clause with three concrete trigger scenarios. This matches the anchor 5 example's structure of clear what + explicit when with concrete trigger phrases; anchor 4's 'when could be more explicit' does not apply here.

5 / 5

Trigger Term Quality

Includes natural terms users would say — 'selecting a prioritization method', 'comparing frameworks like RICE vs ICE', plus framework names that serve as strong triggers. A few common natural phrases are missing (e.g., 'feature ranking', 'roadmap prioritization', 'impact vs effort'), which keeps it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The prioritization-frameworks niche with named frameworks (RICE, ICE, Kano, MoSCoW) is mostly distinct with clear triggers. Minor overlap risk remains with general product-management, decision-making, or task-prioritization skills — 'prioritization' is a broad term and the skill even includes Eisenhower Matrix for personal tasks — so anchor 5's 'minimal conflict risk' is not fully met.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-execution/skills/prioritization-frameworks/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.