Borrowing it
Nothing to install: this file belongs to MrJoeSack/pm-prompts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MrJoeSack/pm-prompts/main/.claude/commands/prioritization.mdgit clone --depth 1 https://github.com/MrJoeSack/pm-promptsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/mrjoesack/pm-prompts/prioritization)<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/prioritization"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/prioritization/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/prioritization"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/prioritization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.00554 |
| Opus 5.5 | $0.00008 | $0.00222 |
| Sonnet 5.5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
prioritization scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Prioritization
I'll help you prioritize features and initiatives using established scoring frameworks: RICE, ICE, and Kano model.
Prioritization Methods
RICE Framework
- Reach: Number of users/customers affected per quarter
- Impact: Impact per user (0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive)
- Confidence: Confidence in reach and impact estimates (%)
- Effort: Person-months of development work
- Score: (Reach × Impact × Confidence) ÷ Effort
ICE Framework
- Impact: Business impact potential (1-10 scale)
- Confidence: Confidence in success (1-10 scale)
- Ease: Ease of implementation (1-10 scale)
- Score: (Impact + Confidence + Ease) ÷ 3
Kano Model
- Basic Needs: Must-have features (dissatisfiers if missing)
- Performance Needs: More is better (satisfiers)
- Excitement Needs: Unexpected delighters
- Indifferent: Features users don't care about
- Reverse: Features that actually hurt satisfaction
What I Need
Feature List:
- Feature names and descriptions
- Target user segments
- Business objectives
Context Information:
- Team capacity (people and time)
- Strategic priorities
- Technical constraints
- Market pressures
Estimation Data:
- User reach estimates
- Development effort estimates
- Success confidence levels
- Expected business impact
Analysis Process
1. Feature Scoring
- Apply RICE scoring to quantify priority
- Use ICE for quick comparative analysis
- Categorize features using Kano model
2. Portfolio Balancing
- Mix of basic needs, performance, and excitement features
- Balance quick wins vs. strategic bets
- Consider technical debt and infrastructure needs
3. Capacity Allocation
- Map high-priority features to team capacity
- Account for technical complexity and dependencies
- Plan for iteration and learning cycles
Output Format
Priority Matrix
- Features ranked by RICE/ICE scores
- Kano categorization for each feature
- Effort vs. impact visualization
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 85 lines · 19 tokens per session scan A df2884b7cb15
prioritization is a command published in the GitHub repository MrJoeSack/pm-prompts (6 stars, last pushed 9mo ago), licensed MIT. It adds 19 tokens to every session and 554 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
prioritization compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| prioritizationMrJoeSack/pm-prompts | Command | 6 | 9mo ago | MIT | A | 19 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |