stakeholder-mapping — Claude Code skill: what it does, how to install
Maps stakeholders across two 2x2 grids to balance executive priorities against the needs of impacted users who lack organizational authority.
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a claude-codeWhat stakeholder-mapping does
The skill plots project participants on two separate 2x2 grids. The Power × Interest matrix sets your communication approach, determining whether a stakeholder needs close partnership, executive briefings, or regular status notes.
Relying solely on that classic grid risks favoring executive authority while ignoring end users. The Impact × Power matrix flags individuals who bear the brunt of changes but lack decision-making weight. Comparing both outputs uncovers hidden risks and informs quadrant migration.
Arriving without a prepared list forces the agent to collect names from scratch, extending work beyond the estimated 25 to 40 minutes. Feed its outputs into stakeholder-engagement-advisor to draft specific outreach plans.
What it helps with
- categorize stakeholders by influence and engagement level
- surface affected user groups that lack decision-making power
- build an engagement plan before roadmap reviews
- reassess stakeholder dynamics after an internal reorg
Example prompts for the agent
- Map our 14 billing migration stakeholders across both grids, roles attached
- Find which user groups lack a voice in our upcoming roadmap update
- Analyze executive power versus team impact for this compliance overhaul
How to install stakeholder-mapping
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a claude-code2Manually: put the files in place
~/.claude/skills/stakeholder-mapping/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stakeholder-mapping/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a codex2Manually: put the files in place
.agents/skills/stakeholder-mapping/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a cursor2Manually: put the files in place
.cursor/skills/stakeholder-mapping/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills stakeholder-mapping2Manually: put the files in place
.github/skills/stakeholder-mapping/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/stakeholder-mappingManually: put the files in place
.devin/skills/stakeholder-mapping/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about stakeholder-mapping
How do I install stakeholder-mapping in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -a claude-code. The skill file installs to ~/.claude/skills/stakeholder-mapping/SKILL.md.
What is the purpose of running two separate grids?
Power × Interest determines how often to brief executives, while Impact × Power reveals who suffers the consequences of failure without having authority. Comparing them stops teams from building for the wrong priorities.
What other skills does this workflow rely on?
It works best with input lists from stakeholder-identification and hands off the analyzed quadrants directly to stakeholder-engagement-advisor.