[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A09NDFJAG1NET62DJKKBXN":3,"skill-same:01M7A09NDFJAG1NET62DJKKBXN":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7A09NDFJAG1NET62DJKKBXN","prioritization-frameworks",null,"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.","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-execution\u002Fskills\u002Fprioritization-frameworks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prioritization-frameworks\ndescription: \"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.\"\n---\n\n## Prioritization Frameworks Reference\n\nA reference guide to help you select and apply the right prioritization framework for your context.\n\n### Core Principle\n\nNever allow customers to design solutions. Prioritize **problems (opportunities)**, not features.\n\n### Opportunity Score (Dan Olsen, *The Lean Product Playbook*)\n\nThe recommended framework for prioritizing customer problems.\n\nSurvey customers on **Importance** and **Satisfaction** for each need (normalize to 0–1 scale).\n\nThree related formulas:\n- **Current value** = Importance × Satisfaction\n- **Opportunity Score** = Importance × (1 − Satisfaction)\n- **Customer value created** = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after\n\nHigh Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot. Prioritizes customer problems, not solutions.\n\n### ICE Framework\n\nUseful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.\n\n- **I** (Impact) = Opportunity Score × Number of Customers affected\n- **C** (Confidence) = How confident are we? (1-10). Accounts for risk.\n- **E** (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.\n\n**Score** = I × C × E. Higher = prioritize first.\n\n### RICE Framework\n\nSplits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.\n\n- **R** (Reach) = Number of customers affected\n- **I** (Impact) = Opportunity Score (value per customer)\n- **C** (Confidence) = How confident are we? (0-100%)\n- **E** (Effort) = How much effort to implement? (person-months)\n\n**Score** = (R × I × C) \u002F E\n\n### 9 Frameworks Overview\n\n| Framework | Best For | Key Insight |\n|-----------|----------|-------------|\n| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |\n| Impact vs Effort | Tasks\u002Finitiatives | Simple 2×2 — quick triage, not rigorous for strategic decisions |\n| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |\n| **Opportunity Score** | Customer problems | **Recommended.** Importance × (1 − Satisfaction). Normalize to 0–1. |\n| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |\n| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |\n| **ICE** | Ideas\u002Finitiatives | Impact × Confidence × Ease. Recommended for quick prioritization. |\n| **RICE** | Ideas at scale | (Reach × Impact × Confidence) \u002F Effort. Adds Reach to ICE. |\n| MoSCoW | Requirements | Must\u002FShould\u002FCould\u002FWon't. Caution: project management origin. |\n\n### Templates\n\n- [Opportunity Score intro (PDF)](https:\u002F\u002Fdrive.google.com\u002Ffile\u002Fd\u002F1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW\u002Fview)\n- [Importance vs Satisfaction Template — Dan Olsen (Google Slides)](https:\u002F\u002Fdocs.google.com\u002Fpresentation\u002Fd\u002F1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M\u002Fedit#slide=id.g796641d975_0_3)\n- [ICE Template (Google Sheets)](https:\u002F\u002Fdocs.google.com\u002Fspreadsheets\u002Fd\u002F1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-\u002Fedit?usp=share_link&ouid=111307342557889008106&rtpof=true&sd=true)\n- [RICE Template (Google Sheets)](https:\u002F\u002Fdocs.google.com\u002Fspreadsheets\u002Fd\u002F1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv\u002Fedit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true)\n\n---\n\n### Further Reading\n\n- [The Product Management Frameworks Compendium + Templates](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-product-frameworks-compendium)\n- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fkano-model-how-to-delight-your-customers)\n- [Continuous Product Discovery Masterclass (CPDM)](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fcpdm) (video course)\n","## Prioritization Frameworks Reference\n\nA reference guide to help you select and apply the right prioritization framework for your context.\n\n### Core Principle\n\nNever allow customers to design solutions. Prioritize **problems (opportunities)**, not features.\n\n### Opportunity Score (Dan Olsen, *The Lean Product Playbook*)\n\nThe recommended framework for prioritizing customer problems.\n\nSurvey customers on **Importance** and **Satisfaction** for each need (normalize to 0–1 scale).\n\nThree related formulas:\n- **Current value** = Importance × Satisfaction\n- **Opportunity Score** = Importance × (1 − Satisfaction)\n- **Customer value created** = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after\n\nHigh Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot. Prioritizes customer problems, not solutions.\n\n### ICE Framework\n\nUseful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.\n\n- **I** (Impact) = Opportunity Score × Number of Customers affected\n- **C** (Confidence) = How confident are we? (1-10). Accounts for risk.\n- **E** (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.\n\n**Score** = I × C × E. Higher = prioritize first.\n\n### RICE Framework\n\nSplits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.\n\n- **R** (Reach) = Number of customers affected\n- **I** (Impact) = Opportunity Score (value per customer)\n- **C** (Confidence) = How confident are we? (0-100%)\n- **E** (Effort) = How much effort to implement? (person-months)\n\n**Score** = (R × I × C) \u002F E\n\n### 9 Frameworks Overview\n\n| Framework | Best For | Key Insight |\n|-----------|----------|-------------|\n| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |\n| Impact vs Effort | Tasks\u002Finitiatives | Simple 2×2 — quick triage, not rigorous for strategic decisions |\n| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |\n| **Opportunity Score** | Customer problems | **Recommended.** Importance × (1 − Satisfaction). Normalize to 0–1. |\n| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |\n| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |\n| **ICE** | Ideas\u002Finitiatives | Impact × Confidence × Ease. Recommended for quick prioritization. |\n| **RICE** | Ideas at scale | (Reach × Impact × Confidence) \u002F Effort. Adds Reach to ICE. |\n| MoSCoW | Requirements | Must\u002FShould\u002FCould\u002FWon't. Caution: project management origin. |\n\n### Templates\n\n- [Opportunity Score intro (PDF)](https:\u002F\u002Fdrive.google.com\u002Ffile\u002Fd\u002F1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW\u002Fview)\n- [Importance vs Satisfaction Template — Dan Olsen (Google Slides)](https:\u002F\u002Fdocs.google.com\u002Fpresentation\u002Fd\u002F1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M\u002Fedit#slide=id.g796641d975_0_3)\n- [ICE Template (Google Sheets)](https:\u002F\u002Fdocs.google.com\u002Fspreadsheets\u002Fd\u002F1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-\u002Fedit?usp=share_link&ouid=111307342557889008106&rtpof=true&sd=true)\n- [RICE Template (Google Sheets)](https:\u002F\u002Fdocs.google.com\u002Fspreadsheets\u002Fd\u002F1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv\u002Fedit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true)\n\n---\n\n### Further Reading\n\n- [The Product Management Frameworks Compendium + Templates](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-product-frameworks-compendium)\n- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fkano-model-how-to-delight-your-customers)\n- [Continuous Product Discovery Masterclass (CPDM)](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fcpdm) (video course)\n",{"name":5,"description":7},"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fpm-skills\u002Fpm-execution\u002Fskills\u002Fprioritization-frameworks","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kongnakornna\u002Fgolangapi --skill prioritization-frameworks",{"tool":38,"command":39},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill prioritization-frameworks",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill prioritization-frameworks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-execution\u002Fskills\u002Fprioritization-frameworks\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]