prioritization-frameworks
Apply structured prioritization methods (RICE, value vs effort, MoSCoW, Kano, opportunity scoring, etc.) to make transparent, defensible product trade-offs. Use when ranking roadmap items, features, bugs, or opportunities under constrained resources.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- prioritization-frameworks
- description
- Apply structured prioritization methods (RICE, value vs effort, MoSCoW, Kano, opportunity scoring, etc.) to make transparent, defensible product trade-offs. Use when ranking roadmap items, features, bugs, or opportunities under constrained resources.
03 SKILL.md 正文
Prioritization Frameworks
Overview
Prioritization is continuous and political. Frameworks do not remove judgment; they make assumptions visible and discussions more productive.
When to Use
- Building or revising a roadmap
- Ranking a backlog of opportunities or features
- Resolving competing stakeholder requests
- Communicating why something is (or is not) being done
Common Frameworks
- RICE — Reach, Impact, Confidence, Effort
- Value vs Effort — Simple 2x2 for quick triage
- MoSCoW — Must / Should / Could / Won’t
- Kano — Basic / Performance / Delighters
- Opportunity Scoring — Importance vs satisfaction gaps
- Cost of Delay — Economic framing of urgency
Principles
- Make scoring criteria and assumptions explicit
- Involve the right people; prioritization is a team sport
- Revisit scores when new evidence appears
- Don’t let the framework become bureaucracy — use the lightest method that improves decisions
- Separate “now” from “later” and from “never”
Verification
- [ ] Criteria and scores are understandable to stakeholders
- [ ] Top priorities have clear rationale
- [ ] Deprioritized items are acknowledged, not silently dropped
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.