Skip to main content
command CX Codex

stakeholder-map — Claude Code command: influence grid and communication plan

stakeholder-map — a command that maps stakeholders on a Power × Interest grid and builds a communication plan. Use it when a project affects different groups and you need to ensure each receives the right information at the right time.

MIT ★ 28,211 updated 2026-10-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skills
Open on GitHub

What stakeholder-map does

The command helps you identify everyone affected by your initiative and figure out what each group needs to know. You describe the project — a platform launch, pricing change, or any initiative. It asks about the phase, known groups, and any political dynamics, then suggests stakeholders you might have missed: adjacent teams, on-call engineers, customer success, documentation.

Next, it places each stakeholder on a matrix: horizontal axis shows interest, vertical shows power to influence the outcome. Four quadrants emerge: those who need constant updates (high power, high interest), those you keep in the loop but who are less involved (high power, low interest), those who pay attention but don't decide (low power, high interest), and the rest. The output is a table with communication tiers: channel, frequency, content, owner. Plus a section on potential conflicts, escalation paths, and a RACI matrix for key decisions.

What it helps with

  • identify who to notify about a project and in what order
  • plan communication so conflicts surface and resolve before launch
  • surface stakeholders you might forget
  • build relationships with people who can block decisions

Example prompts for the agent

  • /stakeholder-map New analytics platform launch
  • /stakeholder-map Pricing model change affecting all customers
  • /stakeholder-map and upload a project brief or org chart

How to install stakeholder-map

1Plugin marketplace

/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skills

2Manually: put the files in place

.claude/commands/stakeholder-map.md

Call it with /stakeholder-map. For all projects use ~/.claude/commands/

Questions about stakeholder-map

How do I install stakeholder-map in Claude Code?

Run three commands in order: /plugin marketplace add phuryn/pm-skills, then /plugin install pm-execution@pm-skills. The command file is at .claude/commands/stakeholder-map.md.

What does stakeholder-map do?

It finds everyone affected by your project, places them on a power and interest matrix, and builds a communication plan: who gets what information, how often, and through which channel. Output includes communication tables, owners, and a RACI matrix for decisions.

Who does the command help you remember?

It often surfaces adjacent teams, on-call engineers, support specialists, and documentation teams — people who usually find out about projects after the fact. The command prompts you to consider them so they hear it from you first.

Source text

stakeholder-map.md · MIT
---
description: Map stakeholders on a Power × Interest grid and create a tailored communication plan
argument-hint: "<project, initiative, or launch>"
---

# /stakeholder-map -- Stakeholder Mapping & Communication Plan

Identify all stakeholders for a project, map them by influence and interest, and generate a communication plan that ensures the right people get the right information at the right time.

## Invocation

```
/stakeholder-map New analytics platform launch
/stakeholder-map Pricing model change affecting all customers
/stakeholder-map [upload a project brief or org chart]
```

## Workflow

### Step 1: Understand the Initiative

Ask:
- What is the project or initiative?
- What phase is it in? (planning, building, launching, post-launch)
- Who are the obvious stakeholders you already know about?
- Are there any politically sensitive dynamics to be aware of?

### Step 2: Identify Stakeholders

Brainstorm stakeholders the user might not have considered:
- **Internal**: Engineering, Design, QA, Data, Legal, Finance, Marketing, Sales, Support, Leadership
- **External**: Customers, partners, vendors, regulators, board members
- **Often missed**: Adjacent teams, on-call engineers, customer success, documentation team

### Step 3: Map to Power × Interest Grid

Apply the **stakeholder-map** skill:

Place each stakeholder in a quadrant:

```
                    HIGH INTEREST
                         │
    KEEP SATISFIED       │      MANAGE CLOSELY
    (High Power,         │      (High Power,
     Low Interest)       │       High Interest)
                         │
   ──────────────────────┼──────────────────────
                         │
    MONITOR              │      KEEP INFORMED
    (Low Power,          │      (Low Power,
     Low Interest)       │       High Interest)
                         │
                    LOW INTEREST
```

### Step 4: Generate Communication Plan

```
## Stakeholder Map: [Initiative]

### Stakeholder Grid
| Stakeholder | Role | Power | Interest | Quadrant | Stance |
|------------|------|-------|----------|----------|--------|

### Communication Plan

#### Manage Closely (High Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|

#### Keep Satisfied (High Power, Low Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|

#### Keep Informed (Low Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|

#### Monitor (Low Power, Low Interest)
[Minimal communication — include in broad updates only]

### Potential Conflicts
[Where stakeholder interests may clash — with mitigation strategies]

### Escalation Path
[Who to go to when decisions are blocked]

### RACI Matrix
| Decision Area | Responsible | Accountable | Consulted | Informed |
|--------------|-------------|-------------|-----------|----------|
```

Save as markdown.

### Step 5: Offer Next Steps

- "Want me to **draft the first stakeholder update** for the 'Manage Closely' group?"
- "Should I **create a meeting prep brief** for key stakeholder conversations?"
- "Want me to **set up a communication cadence** as a recurring checklist?"

## Notes

- The "Manage Closely" quadrant is where PMs spend most of their political capital — get these relationships right
- "Stance" (supportive, neutral, resistant) helps prioritize where to invest relationship-building effort
- Don't forget downstream stakeholders: support, docs, and sales enablement teams are often surprised by launches
- Update the map as the project evolves — stakeholder interest shifts with project phase

© Paweł Huryn · MIT · phuryn/pm-skills

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set120

The whole set →
competitive-analysis The competitive-analysis slash command maps a market, compares direct and indirect competitors, and surfaces ways to position a product differently. CX Codex +1 ★ 28,211repo stars plan-okrs plan-okrs generates three OKR sets that connect team goals to company strategy. Each OKR pairs a qualitative objective with three to five measurable key results. CX Codex +1 ★ 28,211repo stars analyze-feedback analyze-feedback processes reviews, NPS surveys, and support tickets into structured markdown reports with sentiment metrics and recurring themes. CX Codex +1 ★ 28,211repo stars pre-mortem The pre-mortem command stress-tests a PRD, launch plan, or feature before release by finding failure risks and turning them into follow-up actions. CX Codex +1 ★ 28,211repo stars battlecard Generates a concise, sales-focused competitive battlecard comparing two products. Useful before prospect calls to align pricing rebuttals and differentiators. CX Codex +1 ★ 28,211repo stars write-stories write-stories is a Claude Code command that turns a feature brief or PRD into backlog items with acceptance criteria. Choose user stories, job stories, or WWA. CX Codex +1 ★ 28,211repo stars analyze-test analyze-test is a Claude Code command that evaluates A/B test results, checks statistical significance and sample size, and recommends whether to ship, extend, or stop. CX Codex +1 ★ 28,211repo stars north-star Identifies your North Star Metric, validates it against core criteria, and outlines actionable input metrics. CX Codex +1 ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open