Stakeholder comms plan
Skill janellecipriano/pm-skills/skills/stakeholder-comms-plan
Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.
npx -y skills add janellecipriano/pm-skills --skill stakeholder-comms-planAssembled 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.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.0 KB, 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-summaryas 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.