agentleFS
Sign inStart free
yuusakuriyuusakuri/agent-skills/skills/stakeholder-map/SKILL.md

stakeholder-map

Skill2 starsChanged 21 days agoMITView on GitHub

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.

16 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides files (org charts, project briefs, team rosters), read them first.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free