Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, the all-hands/company message, the affected-employee message, a manager guide with talking points, a staying-team message, and an external/press holding line.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add mohitagw15856/pm-claude-skills --skill layoff-communication --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Layoff Communication?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mohitagw15856-layoff-communication-pm-claude-skills)More formats (shields.io, HTML) on the badges page.
---
name: layoff-communication
description: "Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, the all-hands/company message, the affected-employee message, a manager guide with talking points, a staying-team message, and an external/press holding line."
---
# Layoff Communication Skill
A layoff is the hardest thing a company communicates, and people remember exactly how it was handled. This skill
plans and writes the full set of messages so affected people learn first and with dignity, managers know what to
say, and the remaining team isn't left in fear — clear, humane, and consistent across every audience.
> **Note:** this produces communications, not legal advice. Layoffs carry legal/regulatory requirements
> (notice periods, protected classes, severance, WARN-type rules) that vary by jurisdiction — the output flags
> where to involve HR and legal counsel and must be reviewed before use.
## Working from a brief
Given "we're cutting 15% next week", **produce the full package anyway** — infer the likely audiences, sequence,
and questions, label assumptions, and bracket the specifics (numbers, dates, severance terms) to confirm. Never
withhold for missing detail; flag every legally sensitive point for HR/legal review.
## Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- **The decision** — scale, which teams/roles, and the timing.
- **The why** — the honest business reason (be specific, not euphemistic).
- **Support offered** — severance, benefits continuation, outplacement, references.
- **Logistics** — how/when affected people are told, access timing, and who delivers each message.
- **Constraints** — legal/regulatory requirements and approvals (flag for counsel).
## Output Format
### Layoff Communications: [company]
**1. Sequencing plan** — who hears what, from whom, and in what order (affected people first and individually,
then the staying team, then external) — with timing so no one finds out via rumour or the wrong channel.
**2. Affected-employee message** — delivered live where possible, with a written follow-up: clear that their
role is ending, the reason, what support they get, exact next steps and dates, and where to get help. Direct,
respectful, no false hope, no jargon.
**3. Company / all-hands message** — the leader's message to everyone: what's happening, why, accountability,
care for those leaving, and what comes next for the team. Owns the decision; doesn't hide behind passive voice.
**4. Manager guide & talking points** — what managers say in the conversations, what to do and avoid, how to
answer the hard questions, and how to support both those leaving and those staying.
**5. Staying-team message** — acknowledges the loss, explains what changes, and rebuilds stability and direction
(survivors need honesty, not forced positivity).
**6. External / press holding line** — a brief, respectful statement if it becomes public.
**7. FAQ** — the questions everyone will ask (pay, benefits, references, timeline, why-me, why-now) with honest answers.
## Quality Checks
- [ ] Affected people are told first, individually, and with dignity — never by mass email or last
- [ ] The business reason is stated honestly and specifically, not in euphemism
- [ ] Support (severance, benefits, outplacement, references) is concrete and clear
- [ ] Managers have actual words and answers, not just "be empathetic"
- [ ] The staying team gets honesty and direction, not forced positivity
- [ ] Every legally sensitive element is flagged for HR/legal review
## Anti-Patterns
- [ ] Do not hide behind euphemism ("rightsizing", "graduating talent") — name it plainly and humanely
- [ ] Do not let affected people learn via the all-hands, press, or rumour — sequence individuals first
- [ ] Do not use passive voice to dodge accountability — leadership owns the decision
- [ ] Do not over-promise or give false hope about reversal or rehire
- [ ] Do not treat this as legal advice — flag jurisdiction-specific obligations for counsel
## Based On
Workforce-change communication practice — dignity-first sequencing, honest rationale, concrete support, manager enablement, and survivor communication.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!