skills/layoff-communication/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills layoff-communicationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
Ask for these only if they aren't already provided (else infer and label):
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.
Workforce-change communication practice — dignity-first sequencing, honest rationale, concrete support, manager enablement, and survivor communication.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.