Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Search & research

pm-prioritize

Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do NOT auto-trigger. Triggers on "/pm-prioritize", "/prioritize", "приоритизация", "ранжируй бэклог", "RICE-анализ", "prioritize requirements", "RICE", "ICE", "MoSCoW", "Kano", "rank backlog".

serejaris · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add serejaris/personal-corp-os --skill pm-prioritize

About this skill


name: pm-prioritize description: Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do NOT auto-trigger. Triggers on "/pm-prioritize", "/prioritize", "приоритизация", "ранжируй бэклог", "RICE-анализ", "prioritize requirements", "RICE", "ICE", "MoSCoW", "Kano", "rank backlog".

pm-prioritize — Rank requirements with RICE / ICE / MoSCoW / Kano

Part of the Personal Corp framework — running a one-person business through AI agents.

Rank a list of requirements using a structured framework. A built-in decision tree picks the right framework based on data availability and decision context. Output is transparent and traceable, so a team can argue with the scores instead of the recommendation.

Inputs

FieldRequiredNotes
Requirement listyesName + brief description; ≥ 3 items. Can take a pain-point list from /pm-feedback or a feature list from /pm-prd
FrameworknoRICE / ICE / MoSCoW / Kano; auto-recommended if not given
Business goalnoCurrent focus (growth / retention / revenue / efficiency); affects weighting
Resource constraintnoAvailable dev capacity (person-days or Story Points)

Optional config

Most of the skill works out-of-box. If you want stable defaults across runs, add an ## Prioritize Config section to your project's CLAUDE.md:

## Prioritize Config

### Default framework (optional)
If unset, the skill auto-recommends per the decision table below.
- default_framework: RICE | ICE | MoSCoW | Kano

### Default resource constraint (optional)
Used in the Sprint allocation step. Skip if you'd rather state it per run.
- sprint_capacity: 20 person-days per Sprint

### Backlog source (optional)
Where the skill should fetch the requirement list from when you don't paste one.
- backlog_source: gh-issues  # gh-issues | github-project | tasks-file | paste
- gh_owner: your-github-handle
- gh_repo: your-main-repo
- gh_label: backlog
- tasks_file: docs/backlog.md

When a config field is set, the skill uses it silently. When unset, the skill asks (see "When input is incomplete").

Research commands (auto-discovery)

If the user points at a backlog source instead of pasting items, the skill can pull the list itself:

# GitHub issues by label
gh issue list -R $OWNER/$REPO --label $LABEL --state open \
  --json number,title,body --limit 100

# GitHub Project items
gh project item-list $PROJECT_ID --owner $OWNER --format json

# Local backlog file
cat $TASKS_FILE

Step 1 — Pick a framework

If unspecified, recommend per this decision table:

ConditionRecommendedWhy
Have user-impact data per item (DAU, conversion), trustworthyRICEMost quantitative, traceable
Have intuition but no precise dataICEQuick scoring, tolerates subjectivity
Need 4-bucket alignment fast (e.g. team meeting)MoSCoWForces "must" / "won't" consensus
Need to understand requirement nature, plan featuresKanoIdentifies delight features

Framework comparison:

FrameworkUse caseStrengthLimitTime
RICEData-supported quarterly planningMost objective, comparableDepends on data qualityMedium
ICEFast decisions, brainstormingSimple, fastHighly subjectiveLow
MoSCoWRelease planning, stakeholder alignmentForces consensusEasy to put everything in MustLow
KanoFeature planning, satisfaction researchIdentifies delightersNeeds user research dataHigh

Step 2 — Score requirements

RICE (default)

DimensionMeaningScoringCommon error
ReachUsers impacted in one cycleConcrete number ("5000 users/month")"All users theoretically" as Reach
ImpactPer-user impact magnitude3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimalEverything gets 3
ConfidenceConfidence in the estimate100% = data, 80% = indirect evidence, 50% = gut100% with no data
EffortTotal person-months across all rolesIncludes design + dev + QA + integrationCounting only dev

RICE Score = (R × I × C) / E — higher = higher priority.

Calibration mechanism:

  • Score the same dimension across all items first (all R, then all I) — avoids per-item anchoring bias
  • R calibration: pick a baseline ("login: affects 100% of users"), score others relative
  • I calibration: ≤ 50% of items can score 3 — forces differentiation
  • E calibration: must include design (20%) + dev (50%) + QA (20%) + integration (10%)

ICE (fast)

Score 1-10 on each dimension. ICE Score = I × C × E / 10.

DimensionScoring
Impact1 = trivial, 5 = medium, 10 = transformational
Confidence1 = pure guess, 5 = indirect evidence, 10 = A/B test data
Ease1 = very hard (> 3 months), 5 = medium (2-4 weeks), 10 = trivial (< 1 day)

MoSCoW

BucketDefinitionSuggested share
Must HaveWithout it, can't ship; users can't use core feature≤ 60%
Should HaveImportant but has workaround; one-Sprint delay non-fatal~ 20%
Could HaveNice-to-have; better with, fine without~ 10%
Won't Have (this time)Explicitly out of scope; possibly later~ 10%

Common trap: everything ends up Must Have. Counter: cap Must Have at 60%, force trade-offs.

Kano

TypeTraitDetectionStrategy
Must-beAbsence → dissatisfaction; presence → taken for grantedUsers don't ask for it but rage when missingReach passing grade, don't over-invest
One-dimensionalMore = more satisfaction (linear)Users actively r
Read the complete source ↗