[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A0DAXCCNHDSYVGV4WA4KJB":3,"skill-same:01M7A0DAXCCNHDSYVGV4WA4KJB":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},"01M7A0DAXCCNHDSYVGV4WA4KJB","analyze-feature-requests",null,"Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.","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-product-discovery\u002Fskills\u002Fanalyze-feature-requests\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyze-feature-requests\ndescription: \"Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.\"\n---\n\n## Analyze Feature Requests\n\nCategorize, evaluate, and prioritize customer feature requests against product goals.\n\n### Context\n\nYou are analyzing feature requests for **$ARGUMENTS**.\n\nIf the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.\n\n### Domain Context\n\nNever allow customers to design solutions. Prioritize **opportunities (problems)**, not features. Use **Opportunity Score** (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the `prioritization-frameworks` skill for full details and templates.\n\n### Instructions\n\nThe user will describe their product goal and provide feature requests. Work through these steps:\n\n1. **Understand the goal**: Confirm the product objective and desired outcomes that will guide prioritization.\n\n2. **Categorize requests into themes**: Group related requests together and name each theme.\n\n3. **Assess strategic alignment**: For each theme, evaluate how well it aligns with the stated goals.\n\n4. **Prioritize the top 3 features** based on:\n   - **Impact**: Customer value and number of users affected\n   - **Effort**: Development and design resources required\n   - **Risk**: Technical and market uncertainty\n   - **Strategic alignment**: Fit with product vision and goals\n\n5. **For each top feature**, provide:\n   - Rationale (customer needs, strategic alignment)\n   - Alternative solutions worth considering\n   - High-risk assumptions\n   - How to test those assumptions with minimal effort\n\nThink step by step. Save as markdown or create a structured output document.\n\n---\n\n### Further Reading\n\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","## Analyze Feature Requests\n\nCategorize, evaluate, and prioritize customer feature requests against product goals.\n\n### Context\n\nYou are analyzing feature requests for **$ARGUMENTS**.\n\nIf the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.\n\n### Domain Context\n\nNever allow customers to design solutions. Prioritize **opportunities (problems)**, not features. Use **Opportunity Score** (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the `prioritization-frameworks` skill for full details and templates.\n\n### Instructions\n\nThe user will describe their product goal and provide feature requests. Work through these steps:\n\n1. **Understand the goal**: Confirm the product objective and desired outcomes that will guide prioritization.\n\n2. **Categorize requests into themes**: Group related requests together and name each theme.\n\n3. **Assess strategic alignment**: For each theme, evaluate how well it aligns with the stated goals.\n\n4. **Prioritize the top 3 features** based on:\n   - **Impact**: Customer value and number of users affected\n   - **Effort**: Development and design resources required\n   - **Risk**: Technical and market uncertainty\n   - **Strategic alignment**: Fit with product vision and goals\n\n5. **For each top feature**, provide:\n   - Rationale (customer needs, strategic alignment)\n   - Alternative solutions worth considering\n   - High-risk assumptions\n   - How to test those assumptions with minimal effort\n\nThink step by step. Save as markdown or create a structured output document.\n\n---\n\n### Further Reading\n\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-product-discovery\u002Fskills\u002Fanalyze-feature-requests","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 analyze-feature-requests",{"tool":38,"command":39},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill analyze-feature-requests",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill analyze-feature-requests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-product-discovery\u002Fskills\u002Fanalyze-feature-requests\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",[],[]]