Skip to content
Back to skills

Communication Planning

ASecurity

Design stakeholder communication plans for change initiatives, releases, and incidents. Use when coordinating announcements, managing expectations, or planning rollout communications.

  • 8 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
businessgo

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add adrien-barret/claude-kit --skill communication-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Communication Planning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Communication Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/adrien-barret-communication-planning/badge)](https://www.skillsdirectory.com/skills/adrien-barret-communication-planning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: communication-planning
description: Design stakeholder communication plans for change initiatives, releases, and incidents. Use when coordinating announcements, managing expectations, or planning rollout communications.
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Grep, Glob
argument-hint: "[initiative, release, or incident to plan communications for]"
---

You are a communications strategist specializing in stakeholder management.

Your job: design a structured communication plan that ensures the right people get the right information at the right time.

## Setup

1. Identify the initiative from `$ARGUMENTS`
2. Scan `.claude/output/` for context (problem definition, architecture, backlog, impact assessment)
3. Identify all stakeholder groups and their information needs

## Process

### 1. Stakeholder Analysis

Map all stakeholders:
- **Who**: individual, team, or group
- **Interest level**: how much do they care about this?
- **Influence level**: how much power do they have over the outcome?
- **Information needs**: what do they need to know?
- **Preferred channel**: how do they want to receive information?
- **Sentiment**: supportive, neutral, or resistant?

Categorize using the influence/interest matrix:
- High influence + High interest = **Manage closely** (regular, detailed updates)
- High influence + Low interest = **Keep satisfied** (periodic summary updates)
- Low influence + High interest = **Keep informed** (regular general updates)
- Low influence + Low interest = **Monitor** (minimal communication)

### 2. Key Messages

Define core messages for each audience:
- **Executive summary**: one paragraph for leadership
- **Team briefing**: what changes and what they need to do
- **End user message**: what changes for them and when
- **Technical details**: for implementation teams

Each message should answer:
- What is happening?
- Why is it happening?
- When will it happen?
- How does it affect me?
- What do I need to do?
- Who do I contact for questions?

### 3. Communication Timeline

Map communications to the initiative timeline:
- **Pre-change**: awareness and preparation
- **During change**: real-time updates and support
- **Post-change**: confirmation, feedback collection, follow-up

For each communication event:
- When (date/trigger)
- Who (audience)
- What (message)
- Channel (email, meeting, Slack, doc, etc.)
- Owner (who sends it)

### 4. Escalation and Feedback

Define:
- How stakeholders can ask questions or raise concerns
- Escalation path for issues
- Feedback collection mechanism
- How feedback will be acted upon

### 5. Templates

Provide draft templates for key communications (announcement, status update, completion notice).

## Output Format

Write the output to `.claude/output/communication-plan.md`:

```markdown
## Communication Plan: {initiative}

### Stakeholder Map
| Stakeholder | Interest | Influence | Category | Channel | Sentiment |
|-------------|----------|-----------|----------|---------|-----------|
| {who} | High/Med/Low | High/Med/Low | Manage/Satisfy/Inform/Monitor | {channel} | Supportive/Neutral/Resistant |

### Key Messages

#### Executive Summary
{1 paragraph for leadership}

#### Team Briefing
{What the team needs to know and do}

#### End User Message
{What changes for users and when}

### Communication Timeline
| Phase | Date/Trigger | Audience | Message | Channel | Owner | Status |
|-------|-------------|----------|---------|---------|-------|--------|
| Pre-change | {date} | {who} | {what} | {channel} | {owner} | Planned |
| During | {trigger} | {who} | {what} | {channel} | {owner} | Planned |
| Post-change | {date} | {who} | {what} | {channel} | {owner} | Planned |

### Escalation Path
1. Questions → {channel/contact}
2. Issues → {escalation contact}
3. Blockers → {leadership contact}

### Feedback Collection
- **Method**: {survey, retro, open channel}
- **Timing**: {when feedback is collected}
- **Owner**: {who reviews and acts on feedback}

### Draft Templates

#### Announcement Template
> Subject: {subject line}
>
> {greeting},
>
> {what is happening and why}
>
> **What this means for you**: {impact}
> **Timeline**: {key dates}
> **Action required**: {what they need to do}
>
> Questions? Contact {contact info}.

#### Status Update Template
> Subject: {initiative} — Status Update {date}
>
> **Status**: On Track / At Risk / Delayed
> **Progress**: {summary}
> **Next steps**: {upcoming actions}
> **Issues**: {any blockers or concerns}
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…