borghei/Claude-Skills / business-operations/internal-comms
internal-comms
VerifiedPlan, sequence, and pressure-test internal announcements before they send. Use when announcing a reorg, policy, or product change, drafting an all-hands or exec update, or deciding who hears what and in which order.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.5 KB |
| assets/announcement-template.md | markdown | 2.0 KB |
| assets/comms-plan-template.md | markdown | 2.8 KB |
| assets/sample_announcement.json | config | 882 B |
| assets/sample_change.json | config | 840 B |
| assets/sample_message_profile.json | config | 208 B |
| references/announcement-archetypes.md | markdown | 8.4 KB |
| references/change-comms-cadence.md | markdown | 10.3 KB |
| scripts/announcement_auditor.py | script | 9.3 KB |
| scripts/channel_fit_scorer.py | script | 9.6 KB |
| scripts/comms_sequencer.py | script | 10.1 KB |
assets/comms-plan-template.md
View on GitHub# Communication Plan: <change name>
**Type:** <reorg | policy | migration | leadership | bad-news>
**Effective date:** <date>
**Reversible:** <yes / no> — if no, no feedback window
**Blast radius:** <people whose work or employment changes> of <total recipients>
**Embargo:** <none | reason and lift time>
Generate the first draft with `scripts/comms_sequencer.py`, then assign owners.
---
## Sequence
| T-offset | Step | Audience | Channel | Owner | Status |
|----------|------|----------|---------|-------|--------|
| T-5 | Exec pre-brief | <group> | small-group briefing | | |
| T-3 | Influencer pre-brief | <5-10 named people> | 1:1 | | |
| T-2 | Manager enablement | all people managers in scope | 60-min live + FAQ | | |
| T-1 | Customer-facing brief | <group> | team session + holding statement | | |
| T+0 | Broadcast | all staff | all-hands then written | | |
| T+1 | External note | <partners/customers> | account email | | |
| T+3 | FAQ update | all recipients | shared doc + original thread | | |
| T+7 | Manager check-in | people managers | manager forum | | |
| T+14 | Progress note | all recipients | written, under 150 words | | |
| T+28 | Close-out | all recipients | written | | |
---
## Manager enablement pack
- **Talk track** (150-250 words, in their own words): <link>
- **May say now / must wait / must not speculate:** <link>
- **Three hardest questions with real answers:** <link>
- **Escalation route when they do not know:** <named person, response time>
- **Feedback channel back to us:** <channel>, reviewed within 48h of broadcast
## Question routing
| Question type | Goes to | Response commitment |
|---------------|---------|---------------------|
| "What does this mean for my role" | Direct manager | Same day |
| Process / policy detail | <channel> | 1 business day |
| Compensation / employment terms | <HR contact> | 2 business days |
| Anything legal or regulatory | <named counsel> | Do not answer informally |
## Feedback window
**Open / closed:** <closed for irreversible changes>
**If open — scoping sentence:** "We are not revisiting <settled part>. We do want to hear
<specific open part> by <date>."
## Success signals
- [ ] Week-3 questions are about implementation detail, not "what does this mean for me"
- [ ] Manager escalation volume spiked then decayed (flat zero is a bad sign)
- [ ] Required-action completion rate: <target>% by <date>
- [ ] No group learned about this from a peer group rather than from us
## Risks
| Risk | Likelihood | Mitigation |
|------|-----------|------------|
| Leak before broadcast | | Compress cascade window; pre-draft an early-release version |
| Managers cannot answer question 1 | | Enablement session is mandatory, not optional |
| Adjacent celebratory message lands same week | | Hold all non-urgent sends for 48h |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |