stakeholder-map — Claude Code skill: what it does, how to install
Maps stakeholders on a power-interest grid and drafts communication plans for each group. Use it before a launch or when teams need alignment.
npx skills add phuryn/pm-skills --skill stakeholder-map -a claude-codeWhat stakeholder-map does
This skill identifies people and groups connected to an initiative, then places them on a power-interest grid. For each quadrant, it recommends a communication approach, including frequency, channel, key message, and the risk of leaving that group out.
It reads supplied org charts, project briefs, and team rosters first. When given a product or initiative description, it uses that context to infer likely stakeholders. The output includes a table with role, power, interest, strategy, frequency, channel, and message, then saves the map as a Markdown document.
It also flags competing interests and suggests alignment strategies. Inferred stakeholders should be checked, because they come from the initiative description when supporting files are not supplied.
What it helps with
- map stakeholders for an initiative
- classify people by power and interest
- plan communication by stakeholder group
- spot competing stakeholder interests
- save a communication plan as Markdown
Example prompts for the agent
- “Build a stakeholder map for this launch and create a communication plan.”
- “Read the attached org chart and place the relevant people on a power-interest grid.”
- “Find competing interests in this initiative and suggest alignment strategies.”
How to install stakeholder-map
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill stakeholder-map -a claude-code2Manually: put the files in place
~/.claude/skills/stakeholder-map/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stakeholder-map/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill stakeholder-map -a codex2Manually: put the files in place
.agents/skills/stakeholder-map/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill stakeholder-map -a cursor2Manually: put the files in place
.cursor/skills/stakeholder-map/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install phuryn/pm-skills stakeholder-map2Manually: put the files in place
.github/skills/stakeholder-map/SKILL.md1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill stakeholder-map -a gemini-cli2Platform CLI
gemini skills install https://github.com/phuryn/pm-skills --path pm-execution/skills/stakeholder-mapManually: put the files in place
.devin/skills/stakeholder-map/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill stakeholder-map -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about stakeholder-map
How do I install stakeholder-map in Codex?
Run npx skills add phuryn/pm-skills --skill stakeholder-map -a codex. The skill file is placed at .agents/skills/stakeholder-map/SKILL.md.
What does stakeholder-map do?
It maps stakeholders by their power and interest in an initiative. The skill produces a communication table and recommendations for each grid quadrant.
What materials does stakeholder-map read before creating a map?
It reads supplied org charts, project briefs, and team rosters first. It can also use a product or initiative description as context.
Source text
SKILL.md · MIT
--- 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) - 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)
© phuryn · MIT · phuryn/pm-skills