Tactical Internal Change-Management Authoring
This skill produces a complete internal change-management communications package for employee-facing announcements such as re-orgs, layoffs, tool rollouts, policy changes, and leadership transitions. It generates a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points, grounded in Prosci ADKAR and Kotter's 8-step model.
✨ What it does
- Generates a 7-touchpoint communication calendar keyed to the effective date, with channel, owner, ADKAR stage, and key m
- Produces a Kotter 8-step compliant primary announcement with magnitude/tone validation (rejects celebratory framing for
- Creates an audience-segmented FAQ and manager cascade talking points.
- Industry-tuned via --profile (tech-startup, scaleup, enterprise, public-company, non-profit).
- Checks for 8 non-negotiable anti-patterns (e.g., Slack-only for layoffs, passive voice, no follow-up touchpoints).
🎯 When to use it
- When an internal change (re-org, layoff, tool rollout, policy change, leadership transition, acquisition) needs to be announced to employees
- When a draft announcement exists but lacks a touchpoint calendar or manager talking points.
- When you need to pre-answer employee questions with an FAQ before the announcement goes out.
- When a previous announcement failed and you need an anti-pattern audit before the next one.
🚀 How to use
Trigger: /cs:grill-bizops
Trigger by describing the internal change event, e.g., 'all-hands announcement', 'change comms', 're-org announcement', 'manager talking points', or 'layoff comms'. Provide details such as change type, audience segments, magnitude, effective date, and available channels. Run the three scripts in order: change_announcement_builder.py, comms_calendar_builder.py, and comms_template_filler.py, each with --profile and --input as needed.
Example prompts:
Create a comms package for a re-org affecting the engineering team, magnitude high, effective in 2 weeks.
Generate manager talking points for a layoff announcement.
📄 Output: A four-artifact comms package: pre-comm, primary announcement, FAQ, and follow-up, plus a touchpoint calendar and anti-pattern audit.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/business-operations/skills/internal-comms .claude/skills/internal-commsSkill source: business-operations/skills/internal-comms/SKILL.md
⚠️ Good to know
Assumes the decision is already made and the user has authority to publish; does not cover customer-facing comms or strategic change strategy design.
❓ FAQ
What is the minimum number of touchpoints recommended?
Prosci research indicates 5–7 touchpoints are the floor for behavioral change; the skill generates a 7-touchpoint calendar.
Can I use this for a layoff announcement?
Yes, but the magnitude must be set to 'disruptive', and the tool will reject celebratory framing or Slack-only channels.
What if I don't have a sponsor sign-off?
The skill produces a draft, not a publication, without sponsor sign-off.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.