ワンクリックで
communication-plan-generator
Generate stakeholder communication plans and message templates for change initiatives
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Generate stakeholder communication plans and message templates for change initiatives
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Expert Electron application architecture skill for IPC design, main/renderer/preload boundaries, security hardening, performance optimization, packaging strategy, native integration, and cross-platform desktop development. Use when reviewing or designing Electron apps, planning migrations, auditing architecture risks, choosing IPC patterns, diagnosing startup or memory issues, or coordinating related Electron skills.
Generates DrawIO XML diagrams for Amazon Web Services architectures from text descriptions or images. Analyzes existing .drawio files to extract AWS components. Use for AWS architecture diagrams, cloud infrastructure documentation, or when converting AWS diagram images to editable DrawIO format.
Generates DrawIO XML diagrams for Google Cloud Platform architectures from text descriptions or images. Analyzes existing .drawio files to extract GCP components. Use for GCP architecture diagrams, cloud infrastructure documentation, or when converting GCP diagram images to editable DrawIO format.
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
Orchestrate a babysitter run. use this command to start babysitting a complex workflow.
Clean up .a5c/runs and .a5c/processes directories. Aggregates insights from completed/failed runs into docs/run-history-insights.md, then removes old run data and orphaned process files.
| name | communication-plan-generator |
| description | Generate stakeholder communication plans and message templates for change initiatives |
| allowed-tools | ["Read","Write","Glob","Grep","Bash"] |
| metadata | {"specialization":"business-analysis","domain":"business","id":"SK-013","category":"Stakeholder Communication"} |
The Communication Plan Generator skill provides specialized capabilities for creating comprehensive stakeholder communication plans. This skill enables systematic development of communication matrices, message templates, FAQ documents, and multi-channel communication strategies for projects and change initiatives.
Create a communication plan for:
Project: [Project description]
Stakeholder Groups: [List of groups]
Include matrix, templates, and cadence.
Generate communication templates for this change:
[Change description]
Create versions for: executives, managers, end users.
Create an FAQ document for:
[Initiative description]
Address likely questions from each stakeholder group.
Design a multi-channel communication strategy:
[Initiative details]
Available Channels: [List of channels]
Recommend channel mix and content approach.
This skill integrates with the following business analysis processes:
| Audience | Message | Channel | Frequency | Owner | Start Date |
|---|---|---|---|---|---|
| Executives | Strategic updates | Email, Town Hall | Monthly | Sponsor | Week 1 |
| Managers | Operational details | Team meetings | Bi-weekly | PM | Week 2 |
| End Users | Impact & actions | Email, Intranet | As needed | Change Lead | Week 3 |
| Phase | Message Focus | Key Content |
|---|---|---|
| Awareness | Why change | Business drivers, vision |
| Understanding | What's changing | Scope, timeline, impacts |
| Preparation | How to prepare | Training, resources, support |
| Implementation | Go-live details | Cutover, support contacts |
| Reinforcement | Success stories | Benefits realized, recognition |
| Channel | Best For | Limitations |
|---|---|---|
| Detailed information, documentation | Easy to ignore, no discussion | |
| Town Hall | Major announcements, Q&A | Scheduling, one-time event |
| Intranet | Reference material, updates | Requires active visiting |
| Team Meetings | Discussion, feedback | Manager-dependent |
| Video | Demonstrations, personal messages | Production effort |
| Newsletters | Regular updates, stories | Limited engagement |
| Slack/Teams | Quick updates, discussion | Information overload |
SUBJECT: [Clear, action-oriented subject line]
OPENING:
[Why this matters to the reader]
KEY POINTS:
- [Point 1: What's happening]
- [Point 2: What it means for you]
- [Point 3: What you need to do]
TIMELINE:
[Key dates and milestones]
SUPPORT:
[Where to get help, who to contact]
CALL TO ACTION:
[Specific next step]
| Metric | Measurement | Target |
|---|---|---|
| Reach | % of audience who received | 100% |
| Open Rate | % who opened (email) | 70%+ |
| Read Rate | % who read completely | 50%+ |
| Understanding | Survey scores | 4.0/5.0 |
| Action Completion | % who took required action | 90%+ |
| Message Type | Recommended Sender |
|---|---|
| Strategic vision | Executive sponsor |
| Operational changes | Project manager |
| Technical details | Technical lead |
| Team impact | Direct manager |
| Support information | Change team |