Stakeholder Map
Produce a power/interest stakeholder map and quadrant-specific communication plan before you commit build resources or launch dates.
Overview
Stakeholder Map is an agent skill most often used in Validate (also Launch distribution, Build pm) that builds a power/interest grid and per-quadrant communication plan for an initiative.
Install
npx skills add https://github.com/phuryn/pm-skills --skill stakeholder-mapWhat is this skill?
- Identifies executives, eng, design, marketing, sales, support, legal, finance, partners, and end users
- Classifies each stakeholder on Power (high/low) and Interest (high/low)
- Places names in Manage Closely, Keep Satisfied, Keep Informed, and Monitor quadrants
- Tailors communication strategy per quadrant (1:1s vs periodic updates vs light touch)
- Accepts org charts, briefs, or rosters when the user attaches files
- Four-quadrant Power × Interest grid (Manage Closely, Keep Satisfied, Keep Informed, Monitor)
Adoption & trust: 1.1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to build or ship something that affects many teams, but you do not know who has veto power versus who only needs a status email.
Who is it for?
Indie founders and solo PMs preparing launches, roadmap changes, or cross-functional bets with limited political bandwidth.
Skip if: Deep org-design exercises or automated CRM stakeholder databases—this is a planning artifact, not a system of record.
When should I use this skill?
When managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
What do I get? / Deliverables
You leave with a labeled stakeholder grid and communication plan so the right people are engaged early and low-power groups are not over-meetinged.
- Stakeholder list with power/interest ratings
- Power × Interest grid placement
- Tailored communication plan by quadrant
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate is the canonical shelf because mapping power and interest clarifies who must approve scope, resourcing, and risk before full Build. Scope subphase captures cross-functional alignment and engagement strategy while the initiative shape is still negotiable.
Where it fits
Map legal and exec sponsors before committing to a pricing-model change.
Define Keep Satisfied updates for sales leadership while engineers stay in Manage Closely for cutover week.
Clarify which support and marketing partners are Keep Informed during a beta feature rollout.
How it compares
A structured PM worksheet in skill form—not a project-management MCP or sprint tooling integration.
Common Questions / FAQ
Who is stakeholder-map for?
Solo builders and small teams who own product delivery and need a fast, explicit map of who influences decisions and how to communicate with each group.
When should I use stakeholder-map?
During Validate when scoping a bet, during Launch when coordinating GTM, or during Build pm when aligning engineering, design, and go-to-market before dates harden.
Is stakeholder-map safe to install?
It processes user-provided context into planning text; review the Security Audits panel on this Prism page and avoid pasting confidential HR data you cannot share with agents.
SKILL.md
READMESKILL.md - Stakeholder Map
## 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)