Productivity
Skill
/stakeholder-map
Build a stakeholder map using a power/interest 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.
Claude Code
$ npx -y skills add phuryn/pm-skills --skill stakeholder-map --agent claude-code
Codex
$ npx skills add phuryn/pm-skills --skill stakeholder-map -a codex -y
Cursor
$ npx skills add phuryn/pm-skills --skill stakeholder-map -a cursor -y
Gemini CLI
$ npx skills add phuryn/pm-skills --skill stakeholder-map -a gemini-cli -y
GitHub Copilot
$ npx skills add phuryn/pm-skills --skill stakeholder-map -a github-copilot -y
OpenCode
$ npx skills add phuryn/pm-skills --skill stakeholder-map -a opencode -y
Windsurf
$ npx skills add phuryn/pm-skills --skill stakeholder-map -a windsurf -y
SKILL.md
stakeholder-map.SKILL.mdname: stakeholder-map
description: "Build a stakeholder map using a power/interest 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."
Stakeholder Mapping & Communication Plan
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
Context
You are helping build a stakeholder map for **$ARGUMENTS**.
If 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.
Instructions
1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
2. **Classify each stakeholder** on two dimensions:
- **Power** (High/Low): Their ability to influence decisions, resources, or outcomes
- **Interest** (High/Low): How much the project directly affects them or how engaged they are
3. **Place stakeholders in the Power × Interest grid**:
| | High Interest | Low Interest | |---|---|---| | **High Power** | **Manage Closely** — Regular 1:1s, involve in decisions, seek their input early | **Keep Satisfied** — Periodic updates, escalate only critical issues | | **Low Power** | **Keep Informed** — Regular status updates, invite to demos, gather feedback | **Monitor** — Light-touch updates, available on request |
4. **For each quadrant**, recommend:
- Communication frequency (daily, weekly, bi-weekly, monthly)
- 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)
- Key messages and framing
- Potential risks if this stakeholder is neglected
5. **Create a communication plan table**:
| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message | |---|---|---|---|---|---|---|---|
6. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies.
Think step by step. Save the stakeholder map as a markdown document.
---
Further Reading
- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)
Read more
name: stakeholder-map description: "Build a stakeholder map using a power/interest 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."
Stakeholder Mapping & Communication Plan
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
Context
You are helping build a stakeholder map for **$ARGUMENTS**.
If 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.
Instructions
1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
2. **Classify each stakeholder** on two dimensions:
- **Power** (High/Low): Their ability to influence decisions, resources, or outcomes
- **Interest** (High/Low): How much the project directly affects them or how engaged they are
3. **Place stakeholders in the Power × Interest grid**:
| | High Interest | Low Interest | |---|---|---| | **High Power** | **Manage Closely** — Regular 1:1s, involve in decisions, seek their input early | **Keep Satisfied** — Periodic updates, escalate only critical issues | | **Low Power** | **Keep Informed** — Regular status updates, invite to demos, gather feedback | **Monitor** — Light-touch updates, available on request |
4. **For each quadrant**, recommend:
- Communication frequency (daily, weekly, bi-weekly, monthly)
- 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)
- Key messages and framing
- Potential risks if this stakeholder is neglected
5. **Create a communication plan table**:
| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message | |---|---|---|---|---|---|---|---|
6. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies.
Think step by step. Save the stakeholder map as a markdown document.
---
Further Reading
- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)
Stats
27,892
Stars
2,883
Forks
Active
Maintenance
MIT
License
Last commit
Created
Ships withpm-skills
72 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
28k72 skills
Stars on GitHub
Momentum
- stars in total
- 28.0k
Other skills on pm-skills.
More skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
@ayghriInstall Skill
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
@titanwingsInstall Skillopenwork-connect
Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.
@different-aiInstall SkillQuestions about stakeholder-map.
- Which coding agents can use stakeholder-map?
- stakeholder-map installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.