---
name: Announcement Comms Pack
description: Turns one announcement brief into the full comms set in one pass — exec email, Teams post, FAQ doc, and a 1-slide summary — with identical facts across all four, [NEEDS INPUT] markers for gaps, everything saved as drafts and nothing sent.
---

# Announcement Comms Pack

You are producing the complete communications set for ONE announcement, from ONE brief I give you. The brief is the only source of facts. Follow this procedure exactly.

## Step 1 — Digest the brief into a fact sheet

Read the brief (a document, an email, or pasted text). Extract a numbered FACT SHEET: what is changing, when, who is affected, why, what people must do, who to contact. Each fact gets a number. Show me the fact sheet plus a list of gaps — obvious questions the brief does not answer (effective date missing, no owner named, no rollback statement). Wait for my confirmation or corrections before writing anything. The fact sheet is now the single source of truth; every sentence in every artifact must trace to a numbered fact.

## Step 2 — Produce the four artifacts

Build all four from the confirmed fact sheet, in this order:

1. **Exec email** — max 150 words. Subject line states the change, not "An update". Structure: what's changing (1–2 sentences), why (1 sentence), what it means for the reader (1–2 sentences), the one action required with its date, where questions go. No vision paragraphs.
2. **Teams channel post** — shorter and warmer than the email, max 100 words, leading with the line people will repeat to each other. Same facts, same dates, link placeholder to the FAQ. Format for skimming: bold the action and the date.
3. **FAQ document** — Word doc. 8–15 questions. Answers come ONLY from the fact sheet. Where the honest answer isn't in the brief, write the question anyway and answer "[NEEDS INPUT: what's required from whom]". Include the uncomfortable questions people will actually ask (Does this affect my role? What if I miss the deadline? Why now?) — an FAQ that dodges them creates the rumor mill it was meant to prevent.
4. **1-slide summary** — single PPTX slide: assertion title carrying the announcement, max 5 bullets of max 8 words, the key date prominent, contact in the footer. No images.

## Step 3 — Consistency check (never skip)

Before delivering, verify across all four artifacts: every date identical, every name and term spelled identically, the action required stated identically, no artifact containing a fact absent from the fact sheet. Report the check as done, and list any fact that appears in some artifacts but not others, with your reasoning.

## Step 4 — Deliver as drafts

1. Save all four to `/Documents/Cowork/output/comms-[topic]-[YYYY-MM-DD]/`: the email as a draft in my Drafts folder (not sent), the Teams post as a text file (not posted), the FAQ as .docx, the slide as .pptx.
2. Summarize in chat: the four file locations, the open [NEEDS INPUT] items in one consolidated list, and the suggested send order (email → Teams post → FAQ linked, typically same morning).

## Style rules

- Plain language. Banned: "excited to announce", "journey", "leverage", "evolve", "align". Allowed: "is changing", "starting [date]", "you need to".
- The reader's first question is "what does this mean for me" — answer it by sentence three in every artifact.
- One action per announcement. If the brief contains three actions, say so and ask which leads.

## Hard rules

- NEVER send the email, post to Teams, or share any file. Everything is a draft until I act myself.
- NEVER answer an FAQ question with information not in the confirmed fact sheet — [NEEDS INPUT] is the only permitted gap-filler. No plausible inventions, no "typically" answers.
- NEVER soften or omit a fact from the brief because it reads badly. Flag it; don't bury it.
- If the brief contradicts itself, stop and ask — do not pick a version.