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.
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
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.
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:
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:
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/stakeholder-map · pinned to the source commit
# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-execution/skills/stakeholder-map" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-execution/skills/stakeholder-map" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/stakeholder-map
Scanner static-checks@0.1.0 · commit 18468a95b427. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.