# How to Create a Stakeholder Map with the stakeholder-map Command

> Learn how to create a stakeholder map using the stakeholder-map command. This guide details the five-step workflow for generating a Power × Interest matrix and communication plan.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-07-01

---

**The `stakeholder-map` command generates a Power × Interest matrix and tailored communication plan by orchestrating a five-step workflow defined in the pm-execution module.**

The `phuryn/pm-skills` repository provides AI-driven project management capabilities through a CLI powered by the Claude plugin. The `stakeholder-map` command, part of the **pm-execution** module, enables product managers to rapidly build comprehensive stakeholder maps by classifying participants according to influence and engagement levels.

## Understanding the stakeholder-map Command Architecture

### Command Definition

The command is declared in [`pm-execution/commands/stakeholder-map.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/stakeholder-map.md). When invoked, it prompts the user for the project or initiative name, or accepts an uploaded brief, then initiates a structured five-step workflow.

### Skill Implementation

The core logic resides in [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md). This skill implementation:

- Identifies all relevant internal and external stakeholders
- Classifies each stakeholder on **Power** (high/low) and **Interest** (high/low)
- Places them on a Power × Interest grid using the quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor
- Generates a communication-plan table and RACI matrix

### Execution Flow

The architecture follows a self-contained pipeline executed entirely by the Claude plugin runtime:

```text
User → /stakeholder-map command → Prompt for initiative details
       │
       └─► Stakeholder-map skill (SKILL.md) reads arguments,
             optionally parses uploaded files,
             builds the grid & tables
       │
       └─► Returns a ready-to-save Markdown document

```

Because the command and skill are pure-text specifications, the workflow remains deterministic and requires no external API calls.

## How to Create a Stakeholder Map

### Basic Text Invocation

Provide the initiative name as an argument:

```text
/stakeholder-map New analytics platform launch

```

### Processing Uploaded Briefs

Upload a project document for the skill to parse and extract context:

```text
/stakeholder-map [upload project-brief.pdf]

```

### Generated Output Structure

The command produces a Markdown document containing a complete stakeholder analysis:

```markdown

## Stakeholder Map: New analytics platform launch

### Stakeholder Grid

| Stakeholder | Role | Power | Interest | Quadrant      | Stance |
|------------|------|-------|----------|---------------|--------|
| VP Engineering | Exec | High | High | Manage Closely | Supportive |
| Marketing Lead | Team | Low  | High | Keep Informed  | Neutral |
| Finance CFO   | Exec | High | Low  | Keep Satisfied | Resistant |
| Intern QA     | Team | Low  | Low  | Monitor        | N/A      |

### Communication Plan

#### Manage Closely

| Stakeholder | Channel | Frequency | Content                 | Owner |
|------------|---------|-----------|-------------------------|-------|
| VP Engineering | 1:1 | Weekly | Roadmap & risk updates | PM |

```

The output also includes suggested follow-up actions, such as drafting stakeholder updates for the "Manage Closely" group or creating meeting prep briefs for key conversations.

## When to Use the stakeholder-map Command

According to the skill description in [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md), invoke this command when you need to:

- Align cross-functional teams before a product launch
- Create communication plans for new features or migrations
- Document stakeholder responsibilities for governance or audit purposes

## Summary

- The `stakeholder-map` command is defined in [`pm-execution/commands/stakeholder-map.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/stakeholder-map.md) and implemented in [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md)
- It creates a Power × Interest matrix with four quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor
- Input can be a simple text string or an uploaded project brief
- Output includes a stakeholder grid, communication plan table, and RACI matrix rendered as a Markdown document
- The workflow runs entirely within the Claude plugin runtime without external dependencies

## Frequently Asked Questions

### What output format does the stakeholder-map command generate?

The command returns a ready-to-save Markdown document containing the stakeholder grid, communication plan, and RACI matrix. This format allows easy editing and sharing across project management tools.

### Can I upload existing project documents to the stakeholder-map command?

Yes. According to the command definition in [`pm-execution/commands/stakeholder-map.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/stakeholder-map.md), you can upload brief files using the syntax `/stakeholder-map [upload filename.pdf]`, which the skill then parses to extract relevant stakeholder information.

### What quadrants does the Power × Interest matrix use?

The skill classifies stakeholders into four quadrants based on Power and Interest levels: **Manage Closely** (high power, high interest), **Keep Satisfied** (high power, low interest), **Keep Informed** (low power, high interest), and **Monitor** (low power, low interest).

### Does the stakeholder-map command require external APIs?

No. As implemented in the `phuryn/pm-skills` repository, the command and skill are pure-text specifications executed by the Claude plugin runtime, making the workflow self-contained and deterministic without external service calls.