[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M749DWJWN641X0GE4TXD8DP1":3,"skill-same:01M749DWJWN641X0GE4TXD8DP1":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},"01M749DWJWN641X0GE4TXD8DP1","stakeholder-map",null,"Build a stakeholder map using a power\u002Finterest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.","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-execution\u002Fskills\u002Fstakeholder-map\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: stakeholder-map\ndescription: \"Build a stakeholder map using a power\u002Finterest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.\"\n---\n\n## Stakeholder Mapping & Communication Plan\n\nMap stakeholders on a Power × Interest grid and create a tailored communication plan for each group.\n\n### Context\n\nYou are helping build a stakeholder map for **$ARGUMENTS**.\n\nIf the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.\n\n### Instructions\n\n1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.\n\n2. **Classify each stakeholder** on two dimensions:\n   - **Power** (High\u002FLow): Their ability to influence decisions, resources, or outcomes\n   - **Interest** (High\u002FLow): How much the project directly affects them or how engaged they are\n\n3. **Place stakeholders in the Power × Interest grid**:\n\n   | | High Interest | Low Interest |\n   |---|---|---|\n   | **High Power** | **Manage Closely** — Regular 1:1s, involve in decisions, seek their input early | **Keep Satisfied** — Periodic updates, escalate only critical issues |\n   | **Low Power** | **Keep Informed** — Regular status updates, invite to demos, gather feedback | **Monitor** — Light-touch updates, available on request |\n\n4. **For each quadrant**, recommend:\n   - Communication frequency (daily, weekly, bi-weekly, monthly)\n   - Communication format (1:1, email, Slack, meeting, dashboard, all-hands or AMA; for a large Keep Informed group, an anonymous live Q&A lets people raise the concerns they wouldn't in a meeting, see the live-qa skill)\n   - Key messages and framing\n   - Potential risks if this stakeholder is neglected\n\n5. **Create a communication plan table**:\n\n   | Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |\n   |---|---|---|---|---|---|---|---|\n\n6. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies.\n\nThink step by step. Save the stakeholder map as a markdown document.\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- [Team Topologies: A Handbook to Set and Scale Product Teams](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fteam-topologies-a-handbook-to-set)\n","## Stakeholder Mapping & Communication Plan\n\nMap stakeholders on a Power × Interest grid and create a tailored communication plan for each group.\n\n### Context\n\nYou are helping build a stakeholder map for **$ARGUMENTS**.\n\nIf the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.\n\n### Instructions\n\n1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.\n\n2. **Classify each stakeholder** on two dimensions:\n   - **Power** (High\u002FLow): Their ability to influence decisions, resources, or outcomes\n   - **Interest** (High\u002FLow): How much the project directly affects them or how engaged they are\n\n3. **Place stakeholders in the Power × Interest grid**:\n\n   | | High Interest | Low Interest |\n   |---|---|---|\n   | **High Power** | **Manage Closely** — Regular 1:1s, involve in decisions, seek their input early | **Keep Satisfied** — Periodic updates, escalate only critical issues |\n   | **Low Power** | **Keep Informed** — Regular status updates, invite to demos, gather feedback | **Monitor** — Light-touch updates, available on request |\n\n4. **For each quadrant**, recommend:\n   - Communication frequency (daily, weekly, bi-weekly, monthly)\n   - Communication format (1:1, email, Slack, meeting, dashboard, all-hands or AMA; for a large Keep Informed group, an anonymous live Q&A lets people raise the concerns they wouldn't in a meeting, see the live-qa skill)\n   - Key messages and framing\n   - Potential risks if this stakeholder is neglected\n\n5. **Create a communication plan table**:\n\n   | Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |\n   |---|---|---|---|---|---|---|---|\n\n6. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies.\n\nThink step by step. Save the stakeholder map as a markdown document.\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- [Team Topologies: A Handbook to Set and Scale Product Teams](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fteam-topologies-a-handbook-to-set)\n",{"name":5,"description":7},"main","9af7bfd0bc47fdad43c2eaa7a43cd13918e7aaef","pm-execution\u002Fskills\u002Fstakeholder-map",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 stakeholder-map",{"tool":40,"command":41},"bunx","bunx skills add phuryn\u002Fpm-skills --skill stakeholder-map",{"tool":43,"command":44},"pnpm","pnpm dlx skills add phuryn\u002Fpm-skills --skill stakeholder-map","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-execution\u002Fskills\u002Fstakeholder-map\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",[],[]]