AutoGineer
Generated banner for Stakeholder Map
Generated logo for Stakeholder Map

Stakeholder Map

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to stakeholder management by categorizing individuals and groups based on their influence and interest levels. By placing stakeholders into a power/interest grid, the agent helps users determine the appropriate engagement strategy for each group, ensuring that communication is efficient, targeted, and effective for project success.

What it does

  • Identifies key stakeholders across various organizational functions.
  • Classifies stakeholders based on their power and interest levels.
  • Maps stakeholders into a four-quadrant power/interest grid.
  • Defines specific communication strategies, frequencies, and channels for each quadrant.
  • Generates a comprehensive communication plan table.
  • Identifies potential conflicts between stakeholders and suggests alignment strategies.

When to use it

  • When preparing for a new product launch or major initiative.
  • When managing complex projects with multiple cross-functional teams.
  • When planning stakeholder engagement for long-term projects.
  • When you need to align diverse groups with competing interests.

Advantages

  • Ensures critical stakeholders receive the appropriate level of attention.
  • Reduces communication overhead by tailoring updates to stakeholder needs.
  • Helps proactively identify and mitigate potential stakeholder conflicts.
  • Provides a clear, actionable framework for project communication.

Usage examples

“Create a stakeholder map for our upcoming mobile app launch.”
The agent identifies the project team, marketing, engineering, and executive leadership, maps them to the power/interest grid, and provides a communication plan table.
“I need a communication plan for the migration of our legacy database.”
The agent analyzes the technical and business stakeholders involved in the migration and generates a structured plan to keep them informed based on their influence.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/stakeholder-map/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip stakeholder-map.zip -d .agents/skills

Documentation by Pawel Huryn

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 InterestLow Interest
    High PowerManage Closely — Regular 1:1s, involve in decisions, seek their input earlyKeep Satisfied — Periodic updates, escalate only critical issues
    Low PowerKeep Informed — Regular status updates, invite to demos, gather feedbackMonitor — 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:

    StakeholderRolePowerInterestStrategyFrequencyChannelKey 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

Files

SKILL.md

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 InterestLow Interest
    High PowerManage Closely — Regular 1:1s, involve in decisions, seek their input earlyKeep Satisfied — Periodic updates, escalate only critical issues
    Low PowerKeep Informed — Regular status updates, invite to demos, gather feedbackMonitor — 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:

    StakeholderRolePowerInterestStrategyFrequencyChannelKey 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

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/stakeholder-map · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download stakeholder-map.zip