← Back to list
⚡

stakeholder-map Checked

Build a stakeholder map using a power/interest grid, identify communication strategies per quadra…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
7.9Overall rating
2Views
5Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "stakeholder-map" skill by following the instructions at https://skill123.me/install/stakeholder-map.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/stakeholder-map.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 1 KB
📊 Static rating
7.9/10
Trigger
7.0
Structure
8.0
Workflow
6.4
Content
9.0
Engineering
9.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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.

Documentation

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.

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

Score breakdown

Trigger
7.0
Description gives What and four When phrasings (launch, alignment, engagement); no When-Not and no Chinese keywords.
Structure
8.0
51-line single file; grid and plan tables inline; body starts at H2; minimal and appropriate.
Workflow
6.4
Six steps with two-dimension classification, quadrant strategies, and conflict flagging; no failure handling or output self-check beyond generic think-step-by-step.
Content
9.0
Clear imperative steps and fully specified tables; no filler.
Engineering
9.0
Valid frontmatter; no scripts; two credible external links; no broken references.
Security
9.5
No scripts, network, secrets, or injection; benign content.
Concise power-interest stakeholder mapping skill with a complete quadrant strategy table and conflict flagging; light on verification and boundary design.