Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Manager cascade message formatter

Converts an executive-level change announcement into a manager-ready cascade packet with simplified talking points, anticipated team questions with answers, discussion prompts, and concrete action items with owners and…

download .md

Purpose

Transform a polished executive communication into a practical cascade packet that frontline managers can actually use — stripping corporate abstraction, surfacing the questions teams will really ask, and giving managers explicit discussion prompts and action items. Solves the "message decay" problem where leadership intent gets diluted or misdelivered by the time it reaches the team.

When to Use

Invoke this skill when the user asks to:

  • Turn a CEO or executive message into a manager talking-points version
  • Create a cascade packet for a change, reorg, or policy rollout
  • Prepare managers to deliver difficult or complex news to their teams
  • Build discussion guides and FAQs for team meetings around an announcement
  • Simplify leadership language into something managers can say in their own words
  • Add action items and follow-up steps to a top-down communication

Inputs Required

Before starting, collect:

  • Executive message: The original leadership communication (paste in full)
  • Audience: Who the managers will cascade to (department, function, seniority, size)
  • Change type: Reorg / strategy shift / policy change / leadership transition / business update / other
  • Sensitivity level: Routine / notable / high-stakes (layoffs, restructure, controversial policy)
  • Cascade deadline: When managers must have delivered this to teams
  • Known concerns: Any anticipated pushback, morale risks, or hot-button topics
  • What managers can and cannot say: Confidential details, embargoed items, or open questions

If sensitivity level or known concerns are missing, assume "notable" and infer likely concerns from the change type, flagging the assumption.

Instructions

Step 1: Extract the Core Message

Read the executive message and distill it to its essentials:

  • The one-sentence takeaway: What is the single thing every team member must walk away understanding?
  • What is changing: State plainly, in the present or near future, without hedging language
  • Why now: The business or people rationale in cause-and-effect terms
  • What is NOT changing: Reassurance points — explicitly name what stays the same (often more calming than the change itself)

Strip out executive-register phrasing: replace "leverage synergies," "strategic realignment," "operating model," and similar abstractions with concrete equivalents a manager would say out loud.

Step 2: Build the Manager Talking Points

Produce 5–8 talking points written in first-person spoken language — how a manager would actually say it in a team huddle, not how it reads on a slide.

  • Lead with the takeaway, not the backstory
  • Each point is 1–2 sentences, conversational, no jargon
  • Include one point that explicitly acknowledges how the change might feel ("I know this raises questions about…")
  • Calibrate candor to the sensitivity level — high-stakes changes require the manager to name the hard part directly

Step 3: Anticipate Team Questions (FAQ)

Generate 6–10 questions teams are likely to actually ask, ordered by how quickly they'll come up. For each:

  • The question (phrased the way a team member would ask it, including the blunt versions)
  • The answer the manager can give — grounded in what they're permitted to say
  • If they don't know: A holding response for open questions ("I don't have that answer yet — here's how I'll get it to you")

Prioritize the questions managers dread: job security, workload, "was this decision already made," "why weren't we consulted."

Step 4: Write Team Discussion Prompts

Provide 3–5 open-ended prompts a manager can use to move the meeting from broadcast to dialogue:

  • Prompts that invite reaction without opening ungovernable debate
  • At least one prompt that surfaces practical impact ("What would make this easier for how we work?")
  • At least one that gives the team a small sense of agency

Step 5: Define Action Items

List 3–6 concrete action items with an owner and a timeframe. Split into:

  • Manager actions: What the manager must do (hold the meeting by X, submit questions to leadership by Y)
  • Team actions: What team members should do, if anything
  • Follow-up loop: How and when the manager reports team questions or sentiment back upward

Every action item has a verb, an owner, and a due date or window — no open-ended "keep in mind" items.

Step 6: Add Delivery Guidance

Give the manager 3–4 short coaching notes on how to deliver this:

  • Tone to set, what to avoid saying, how to handle silence or pushback
  • For high-stakes changes: what to do if someone gets upset, and when to escalate

Output Format

  • Structure: Cascade packet with labeled sections, formatted for a manager to read and use directly
  • Length: 700–1,100 words
  • Format: Structured document — talking points and FAQ as lists, action items as a table with Owner and Due columns
  • Sections: Core Message Summary → Manager Talking Points → Anticipated Questions (FAQ) → Team Discussion Prompts → Action Items → Delivery Guidance
  • Tone: Plain, human, and manager-facing — as if a trusted People partner briefed the manager one-on-one; warm but direct, never corporate

Quality Checklist

Before delivering output, verify:

  • [ ] The one-sentence takeaway is genuinely one sentence and jargon-free
  • [ ] Talking points are written in spoken first-person, not executive slide language
  • [ ] FAQ includes at least one blunt/uncomfortable question the team will actually ask
  • [ ] Every action item has a verb, an owner, and a due date or window
  • [ ] No confidential or embargoed detail from the "cannot say" list appears in the packet
  • [ ] Sensitivity calibration matches the stated level — high-stakes packets name the hard part directly

Notes

  • The most common cascade failure is managers reading the executive message verbatim; the talking points must sound like the manager's own words or they won't be used
  • For layoffs and restructures, always include an escalation path in Delivery Guidance — managers should never improvise on job-security questions
  • If the executive message contains unresolved open items, do not paper over them — give managers an honest "here's what we don't know yet" line, which builds more trust than false certainty

<citations> <document> <document_type>RAG_KNOWLEDGE_BASE</document_type> <document_id>1I5wTZjTKZ6ChVBnnkGw3T</document_id> </document> </citations>

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills