How do I install the Stakeholder Comms Plan skill?

Run npx skillmds@latest add janellecipriano/stakeholder-comms-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Stakeholder Comms Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stakeholder Comms Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stakeholder Comms Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Stakeholder Comms Plan?

janellecipriano (@janellecipriano) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stakeholder Comms Plan by janellecipriano

Name: Stakeholder Comms Plan
Author: janellecipriano

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.

File contents

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.

---name: stakeholder-comms-plandescription: 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.---# Stakeholder Communication PlanIdentify 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.## Process1. **Identify stakeholders** — individuals and groups affected by or influential to the work.2. **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).3. For each, define: **what** they need, **why** (their concern), **cadence**, **channel**, **owner**, and **format**.4. Map to concrete **vehicles** (steering review, weekly status, newsletter, demo, 1:1) — reuse `status-report`/`exec-summary` as the content.5. 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.

Frequently asked questions