Agent skill · writing content · alirezarezvani
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.
Why this skill is useful
Provides a structured framework for internal change communications, including specific templates and sequencing that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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. When to use A re-org / leadership change / new tool rollout / policy change / benefit change / layoff / acquisition close needs internal announcement within 48 hours. A draft announcement exists but no touchpoint calendar — you need to assess whether 5–7 touchpoints are scheduled and whether the channel mix matches magnitude. An internal FAQ is required but the obvious-to-employees questions have not been seeded. Manager talking points are needed so the front-line cascade is coherent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/internal-comms--d7f153