project-template/.claude/skills/communication-planning/SKILL.md
Design stakeholder communication plans for change initiatives, releases, and incidents. Use when coordinating announcements, managing expectations, or planning rollout communications.
npx skillsauth add adrien-barret/claude-kit communication-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
$ARGUMENTS.claude/output/ for context (problem definition, architecture, backlog, impact assessment)Map all stakeholders:
Categorize using the influence/interest matrix:
Define core messages for each audience:
Each message should answer:
Map communications to the initiative timeline:
For each communication event:
Define:
Provide draft templates for key communications (announcement, status update, completion notice).
Write the output to .claude/output/communication-plan.md:
## 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}
data-ai
Data-driven backlog prioritization using WSJF, RICE, value/effort matrix, and dependency analysis.
development
Build a traceability matrix from BMAD artifacts (problem.md, backlog.md, user-journey.md). Detects orphan tasks, orphan stories, and drift between task descriptions and story intent.
development
Generate unit and integration tests for project code. Use when new code is written or test coverage needs improvement.
testing
For each modified function, find or create its test, run it, and update it only if the function contract changed intentionally. Never silently adjust tests to make failures disappear.