Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add killvxk/pm-skills-zh --skill prioritization-frameworksgit clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote 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/skills/killvxk/pm-skills-zh/prioritization-frameworks)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/prioritization-frameworks"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/prioritization-frameworks.svg" alt="Measured on agentmods" 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.00078 | $0.01276 |
| Opus 5 | $0.00039 | $0.00638 |
| Sonnet 5 | $0.00016 | $0.00255 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
prioritization-frameworks 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
优先级框架参考指南
帮助你选择并应用适合当前场景的优先级框架。
Core Principle（核心原则）
永远不要让客户来设计解决方案。优先处理问题（机会），而非功能。
Opportunity Score（机会评分，Dan Olsen，《The Lean Product Playbook》）
推荐用于客户问题优先级排序的框架。
对每个需求向客户调研重要性和满意度（归一化至 0-1 范围）。
三个相关公式：
- 当前价值 = 重要性 × 满意度
- 机会评分 = 重要性 × （1 - 满意度）
- 为客户创造的价值 = 重要性 × （S2 - S1），其中 S1 = 改进前满意度，S2 = 改进后满意度
高重要性 + 低满意度 = 最高机会评分 = 最佳机会。在重要性 vs 满意度图表上绘制——左上象限是黄金区域。优先处理客户问题，而非解决方案。
ICE Framework（ICE 框架）
适用于计划和想法的优先级排序，不仅考虑价值，还考虑风险和经济因素。
- I（影响力 Impact）= 机会评分 × 受影响的客户数量
- C（置信度 Confidence）= 我们有多确定？（1-10）代表风险因素。
- E（简易度 Ease）= 实施难度如何？（1-10）代表经济因素。
评分 = I × C × E。分数越高，优先级越高。
RICE Framework（RICE 框架）
将 ICE 的影响力拆分为两个独立因素，适合需要更细粒度分析的较大团队。
- R（覆盖范围 Reach）= 受影响的客户数量
- I（影响力 Impact）= 机会评分（每位客户的价值）
- C（置信度 Confidence）= 我们有多确定？（0-100%）
- E（工作量 Effort）= 实施工作量？（人月）
评分 = （R × I × C）/ E
9 Frameworks Overview（9 种框架概览）
| 框架 | 最适用场景 | 核心洞察 |
|---|---|---|
| 艾森豪威尔矩阵 | 个人任务 | 紧急 vs 重要——适用于 PM 个人任务管理 |
| 影响力 vs 工作量 | 任务/计划 | 简单 2×2——快速分类，不适合战略决策 |
| 风险 vs 回报 | 计划 | 类似影响力 vs 工作量，但考虑了不确定性 |
| 机会评分 | 客户问题 | 推荐。 重要性 × （1 - 满意度）。归一化至 0-1。 |
| Kano 模型 | 理解用户期望 | 必备型、期望型、兴奋型、无差异型、反向型。用于理解，而非优先排序。 |
| 加权决策矩阵 | 多因素决策 | 对标准赋权，对每个选项打分。适合获得干系人认同。 |
| ICE | 想法/计划 | 影响力 × 置信度 × 简易度。推荐用于快速优先排序。 |
| RICE | 规模化的想法 | （覆盖范围 × 影响力 × 置信度）/ 工作量。在 ICE 基础上增加覆盖范围。 |
| MoSCoW | 需求 | 必须有/应该有/可以有/不会有。注意：源自项目管理领域。 |
Templates（模板）
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.
- 8d ago First seen · 76 lines · 78 tokens per session scan A 6a5b4d22fa86
prioritization-frameworks is a skill published in the GitHub repository killvxk/pm-skills-zh (154 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 1,276 once invoked, about $0.0004 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…