Product-org-os strategy-communication
'Create strategy communication package for aligning stakeholders on strategic direction. Activate when: "communicate the strategy", "strategy deck", "share our direction", stakeholder alignment
git clone https://github.com/yohayetsion/product-org-os
T=$(mktemp -d) && git clone --depth=1 https://github.com/yohayetsion/product-org-os "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/strategy-communication" ~/.claude/skills/yohayetsion-product-org-os-strategy-communication && rm -rf "$T"
skills/strategy-communication/SKILL.mdDocument Intelligence
This skill supports three modes: Create, Update, and Find.
Mode Detection
| Signal | Mode | Confidence |
|---|---|---|
| "update", "revise", "modify" in input | UPDATE | 100% |
| File path provided | UPDATE | 100% |
| "create", "new", "build" in input | CREATE | 100% |
| "find", "search", "list" | FIND | 100% |
| "the communication", "strategy comms" | UPDATE | 85% |
| Just strategy/initiative name | CREATE | 60% |
Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user
Mode Behaviors
CREATE: Generate complete new communication package using template below.
UPDATE:
- Check document registry first, then search user's structure
- Preserve strategic narrative
- Update FAQ, key messages, or communication plan
- Show diff summary
FIND: Check registry, then search user's folders for strategy communications.
Create a Strategy Communication Package for the specified strategy or initiative.
Vision to Value Phase
Phase 3: Strategic Commitments - This skill creates the communication materials after commitments are hardened.
Output Structure
1. Executive Summary
- Strategy overview in 2-3 sentences
- Why now
- Expected outcomes
- Call to action for stakeholders
2. Strategic Narrative
A compelling story that explains:
- Where we've been
- Where we're going
- How we'll get there
- Why this path was chosen
3. Key Messages by Audience
| Audience | Primary Message | Supporting Points | Call to Action |
|---|---|---|---|
| Executives | [Message] | [Points] | [Action] |
| Product team | [Message] | [Points] | [Action] |
| Engineering | [Message] | [Points] | [Action] |
| Sales | [Message] | [Points] | [Action] |
| Customers | [Message] | [Points] | [Action] |
4. Roadmap Highlights
- Key milestones
- What's changing
- What's staying the same
- What's being deprioritized
5. Success Metrics
| Metric | Current | Target | Timeline |
|---|---|---|---|
| [Metric 1] | [Current] | [Target] | [When] |
| [Metric 2] | [Current] | [Target] | [When] |
6. FAQ Document
Q: [Common question 1] A: [Answer]
Q: [Common question 2] A: [Answer]
Q: [Common question 3] A: [Answer]
7. Communication Plan
| Audience | Channel | Timing | Owner | Materials |
|---|---|---|---|---|
| [Audience] | [Channel] | [When] | [Owner] | [Materials] |
8. Presentation Deck Outline
- Title and context
- The opportunity/challenge
- Our strategic response
- Key initiatives
- Timeline and milestones
- Success metrics
- What we need from [audience]
- Q&A
Instructions
- Ask about target audiences if not specified
- Reference any strategy documents provided via @file syntax
- Tailor messages to each audience's concerns
- Include anticipated questions and answers
- Save as markdown file
- Create presentation version using /present