メニュー
Generate stakeholder communication plans and message templates for change initiatives
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/a5c-ai/babysitter --skill communication-plan-generatorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
SKILL.md を表示中
SOC 職業分類に基づく
| 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"} |
| graph | {"domains":["domain:business-intelligence"],"specializations":["specialization:strategic-consulting"],"skillAreas":["skill-area:stakeholder-management","skill-area:change-management","skill-area:business-analysis"],"workflows":["workflow:market-analysis"],"roles":["role:business-analyst","role:organizational-development-specialist"]} |
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 |