Stakeholder map

Skill phuryn/pm-skills/pm-execution/skills/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.From its SKILL.md

Install

npx -y skills add phuryn/pm-skills --skill stakeholder-map

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.5 KB, 495 tokens by cl100k_base, as published. Nobody here has run it

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

Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
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

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

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
Create a communication plan table:

Stakeholder Role Power Interest Strategy Frequency Channel Key Message
Flag potential conflicts: Identify stakeholders with competing interests and suggest alignment strategies.

Think step by step. Save the stakeholder map as a markdown document.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most operations skills give in 495 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

Collect monitoring data throughout the simulationin 14 of 483, across 6 files
Set the random seed for reproducibilityin 14 of 483, across 6 files
Validate simulations against analytical solutionsin 12 of 483, across 4 files
Clarify goals, constraints, and inputsin 11 of 483, across 2 files
Implement contract tests for integration pointsin 11 of 483, across 2 files
Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
Avoid Python blocking calls in processesin 10 of 483, across 3 files
Use resource context managers for automatic cleanupin 9 of 483, across 2 files
Maintain consistent time unitsin 9 of 483, across 2 files
Validate outcomes against success criteriain 8 of 483, across 1 file
Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

flag stakeholders with competing interests
think step by step

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.