[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M749G0DXRFR9PT8XSBFM423E":3,"skill-same:01M749G0DXRFR9PT8XSBFM423E":48},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M749G0DXRFR9PT8XSBFM423E","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.","phuryn\u002Fpm-skills","phuryn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7837354?v=4","01M727RY5RDZZWVRDN2X5F4B1W","Pawel Huryn","01M727RY6H19NE8H5PABTR7A59",27991,"MIT","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-discovery\u002Fskills\u002Fanalyze-feature-requests\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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","9af7bfd0bc47fdad43c2eaa7a43cd13918e7aaef","pm-product-discovery\u002Fskills\u002Fanalyze-feature-requests",2885,"https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills","https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fpm-skills-2-red-team-ship","https:\u002F\u002Fgithub.com\u002Fphuryn","https:\u002F\u002Fwww.productcompass.pm\u002F","AI PM Coach, ex-CPO, Builder | 400K+ Follow","2026-11-09 07:10:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add phuryn\u002Fpm-skills --skill analyze-feature-requests",{"tool":40,"command":41},"bunx","bunx skills add phuryn\u002Fpm-skills --skill analyze-feature-requests",{"tool":43,"command":44},"pnpm","pnpm dlx skills add phuryn\u002Fpm-skills --skill analyze-feature-requests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-discovery\u002Fskills\u002Fanalyze-feature-requests\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M749K1XJGDQ1FA90BGD6MJ6Z","review-resume","Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Freview-resume\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M749JVQ3SER9X0V501S82BRX","privacy-policy","Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fprivacy-policy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M749JRFCNDADS61HFWMBHJJD","grammar-check","Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fgrammar-check\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M749JMXFX9KSXV4JP6J1K7QX","draft-nda","Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fdraft-nda\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M749JGY34DGZ9BGFS2YCET6N","value-proposition","Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fvalue-proposition\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M749JE27D1APC1PWWPFMF2GN","swot-analysis","Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fswot-analysis\u002FSKILL.md",[],[]]