agentleFS
fludofludo/pm-claude-kit/.claude/skills/stakeholder-management/SKILL.md

stakeholder-management

Skill0 starsChanged 6 days agoMITView on GitHub

Map stakeholders and plan/draft communications. Use when the task mentions stakeholders, sponsors, steering committee, clients, power/interest mapping, engagement, escalation emails, difficult conversations, or executive/sponsor updates. PMI Knowledge Areas: Stakeholder + Communications.

4 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep satisfied · Keep informed · Monitor).

    line 13
  2. Very specific:

    Never fabricate status, dates, or commitments ([TBC]).

    line 25

“Common” is measured: kept by at least 6 in 10 of the 4 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 Management

Poor communication is a leading cause of project failure — tailor everything to audience and purpose.

Analysis: build the register and classify on a power/interest grid (Manage closely · Keep satisfied · Keep informed · Monitor). For each stakeholder capture interests, concerns, influence, current vs. desired engagement, and the key message. Use the template at ${CLAUDE_PLUGIN_ROOT}/.claude/skills/pmi-project-management/templates/stakeholder-register.md.

Communications: state audience and purpose up front. For executive comms use situation → impact → options → recommendation → ask. For escalation emails: acknowledge → take ownership → state impact → present options with a recommendation → make the ask → maintain confidence.

Difficult conversations: given scenario, audience, and desired outcome, give talking points, likely objections, and measured responses.

Never fabricate status, dates, or commitments ([TBC]). Flag political judgement calls for the PM. Draft inline; to have a saved draft read as its recipient would, use the stakeholder-analyst agent and pass it the file path or the full text.

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.