Internal Comms
Drafts and sequences an internal-only change-management communication, pairing Prosci ADKAR and Kotter's 8-step model into a touchpoint calendar and message set.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a sensitive announcement. You'd want to be clear about the reasons for the reorganization, how it affects different teams, and what the timeline looks like. It helps to explain the business rationale first, then get into specifics. You should probably address concerns people might have. I'd suggest drafting a message, testing it with a few leaders, and then figuring out how to rollout the communication to avoid surprises. Would you like to start with an outline or a draft?
REORGANIZATION ANNOUNCEMENT - SEQUENCED TOUCHPOINTS TOUCHPOINT 1: LEADERSHIP ALIGNMENT (72 hours before all-hands) Internal memo to department heads: Context on why (market shift toward enterprise, need faster decision-making), timeline (effective 2026-08-15), and key talking points for team 1-1s. TOUCHPOINT 2: ALL-HANDS ANNOUNCEMENT (Day 1, live + recorded) OPENING (Kotter's 8-Step: Create Urgency) "Over the past 18 months, we've gone from 50 to 250 people. Our customer base tripled. Our decision-making velocity hasn't kept pace. This reorganization fixes that." BUSINESS CASE (Communicate Vision) • From product silos to cross-functional pods (each pod owns a customer segment) • Hiring freeze lifted for growth-critical roles (Sales, DevOps) • Engineering velocity target: 2-week feature cycles instead of 4 weeks IMPACT BY ROLE: [SALES]: Dedicated product teams per vertical (Enterprise, Mid-market, SMB). You keep your accounts. [ENGINEERING]: Reorganized into 6 cross-functional pods. Your manager is the product lead. [PEOPLE OPS]: Talent acquisition now focused on pod-level hiring (paired with product). TIMELINE: • Aug 5: New org chart published. Invite 1-1s open. • Aug 15: Org chart effective. First pod all-hands (product visibility). • Aug 29: First post-reorganization retrospective. FAQS (Segmented by audience) FOR SALES: Q: Will this affect my commission or territories? A: No. Your compensation structure remains the same through 2026. FOR ENGINEERING: Q: Are there layoffs implied by this restructure? A: No. We're hiring 8 net new engineers in Q3. Reorganization ≠ reduction. FOR ALL: Q: Why wasn't I consulted in this decision? A: Leadership finalized the structure in private. We'll solicit feedback during the first pod retrospectives (Aug 29). TOUCHPOINT 3: MANAGER CASCADE TALKING POINTS (Aug 5-6) Managers run scripted 1-1s with direct reports using pre-approved talking points. TOUCHPOINT 4: OFFICE HOURS (Aug 7, 2 hours, open Q&A) Leadership answers follow-up questions live. SUCCESS METRICS: • eNPS survey (Aug 15): Expect 35+. Baseline: 42. • Attrition in first 30 days: Target 0% (plan for 1-2% churn). • Pod velocity (by Sept 15): Average 2-week feature cycles. Note: This is not advice on whether to reorganize—only the sequencing framework to minimize surprises and resistance.
About this skill
name: internal-comms description: Use when Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a ...
Internal Comms
Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on "all-hands announcement", "change comms", "rollout comms", "re-org announcement", "manager talking points", "layoff comms".
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the internal-comms skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Internal Comms; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: internal-comms
description: Use this skill to draft and sequence an internal-only change-management communication for employees, such as a re-org announcement, tool rollout, or leadership transition.
version: 1.0.0
category: Business & Ops / Operations
author: AgentVolt
license: proprietary
tags:
- business-ops
- operations
---
# Internal Comms
Drafts and sequences an internal-only change-management communication, pairing Prosci ADKAR and Kotter's 8-step model into a touchpoint calendar and message set.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Capacity Planner
Builds an ops headcount plan using queueing math, P90 demand sizing, and shrinkage-adjusted FTE counts, ending in a quarterly hiring sequence with ramp and attrition built in.
Vendor Management
Runs vendor scorecards, SLA compliance checks, and third-party risk classification for SaaS and supplier relationships.
Procurement Optimizer
Runs structured spend audits, UNSPSC-aligned category analysis, and supplier rationalization.
Business Operations Skills
Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook authoring, procurement spend.