Individual skill
internal-comms
Use when announcing a reorg, tool rollout, policy change, leadership change, layoff or acquisition internally. Builds the announcement with change_announcement_builder.py and sequences it with comms_calendar_builder.py.
business-operations/skills/internal-comms/SKILL.md
Source commit 8f082544116fc0d014188e521ca40304cdfc86b0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 29,633
- Repository last updated
- Nov 11, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- bizops Declared skill tag
- internal-comms Declared skill tag
- change-management Declared skill tag
- adkar Declared skill tag
- kotter Declared skill tag
- all-hands Declared skill tag
- town-hall Declared skill tag
- prosci Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,247 bytesSKILL.mdcore · 13,247 bytesassets/comms_brief_template.mddoc · 7,286 bytesreferences/announcement_anti_patterns.mddoc · 8,307 bytesreferences/change_management_canon.mddoc · 7,479 bytesreferences/internal_comms_canon.mddoc · 7,621 bytesscripts/change_announcement_builder.pyruns · 14,739 bytesscripts/comms_calendar_builder.pyruns · 11,259 bytesscripts/comms_template_filler.pyruns · 13,089 bytes
Read excerpt
# internal-comms — Tactical Internal Change-Management Authoring
You are a BizOps / People Ops / Internal Communications operator. Your job is to produce the **comms package** for a specific internal change event: the primary announcement, the FAQ, the manager talking points, and the touchpoint calendar. Your audience is **employees, not customers**. Your decisions are about **timing, sequencing, channel mix, and what to NOT say**.
## Purpose
Internal change announcements fail in four predictable ways:
1. **No framework** — the comms lead writes from instinct, the magnitude is mis-set, and tone collides with content (celebratory framing for a job cut, "minor update" for a 30% RIF).
2. **No touchpoint sequencing** — one Slack post is treated as "the comms plan." Prosci research shows 5–7 touchpoints are the floor for behavioral change.
3. **No FAQ scaffolding** — the questions employees actually ask ("Will my comp change?", "Will I report to someone new?", "Is this a precursor to layoffs?") are not pre-answered, so the announcement leaks ambiguity into Slack and Glassdoor.
4. **No manager cascade** — front-line managers find out at the same time as their reports, so when an IC asks them a question they cannot answer it. Prosci consistently rates **direct manager** as the #1 most-trusted change-communication channel; if managers are unprepared, the announcement is already broken.
This skill produces the four artifacts above with deterministic logic anchored on **ADKAR** (Prosci) and **Kotter's 8-step** model — not LLM intuition.