Stakeholder comms plan

Skill janellecipriano/pm-skills/skills/stakeholder-comms-plan

Build a stakeholder map and a communication plan — who needs what information, at what cadence, through which channel. Use when the user says "stakeholder map", "communication plan", "comms plan", "who do we need to keep informed", "RACI for comms", or needs to plan how to keep stakeholders aligned across a program.From its SKILL.md

Install

npx -y skills add janellecipriano/pm-skills --skill stakeholder-comms-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 400 tokens by cl100k_base, as published. Nobody here has run it

Stakeholder Communication Plan

Identify everyone who matters to a program and define a deliberate plan for keeping each informed and bought-in.

When to use

Starting a program/project and setting up communications.
Diagnosing why stakeholders feel out of the loop or misaligned.

Inputs to gather

The program and its phase.
Known stakeholders/groups (sponsors, leadership, partner teams, users, vendors).
Existing meetings/channels and any sensitivities.

Process

Identify stakeholders — individuals and groups affected by or influential to the work.
Assess each on interest (how much they care) and influence (how much power), → quadrant:
- High influence / high interest → manage closely (frequent, tailored).
- High influence / low interest → keep satisfied (concise, periodic).
- Low influence / high interest → keep informed (regular updates).
- Low influence / low interest → monitor (minimal).
For each, define: what they need, why (their concern), cadence, channel, owner, and format.
Map to concrete vehicles (steering review, weekly status, newsletter, demo, 1:1) — reuse status-report/exec-summary as the content.
Note risks (skeptics, blockers) and an engagement approach for each.

Output format

## Stakeholder Map — {{program}}
| Stakeholder | Influence | Interest | Strategy | Key concern |
| --- | --- | --- | --- | --- |

## Communication Plan
| Audience | What they get | Cadence | Channel | Format | Owner |
| --- | --- | --- | --- | --- | --- |

Keep it actionable — every row should map to a real, scheduled touchpoint.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most operations skills give in 400 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

Collect monitoring data throughout the simulationin 14 of 483, across 6 files
Set the random seed for reproducibilityin 14 of 483, across 6 files
Validate simulations against analytical solutionsin 12 of 483, across 4 files
Clarify goals, constraints, and inputsin 11 of 483, across 2 files
Implement contract tests for integration pointsin 11 of 483, across 2 files
Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
Avoid Python blocking calls in processesin 10 of 483, across 3 files
Use resource context managers for automatic cleanupin 9 of 483, across 2 files
Maintain consistent time unitsin 9 of 483, across 2 files
Validate outcomes against success criteriain 8 of 483, across 1 file
Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

define what each stakeholder needs
define cadence, channel, owner, and format
map stakeholders to concrete communication vehicles
reuse existing status report or exec summary content
note skeptic or blocker engagement risks
ensure every row maps to a scheduled touchpoint

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.