Skip to content

borghei/Claude-Skills / business-operations/internal-comms

internal-comms

Verified

Plan, sequence, and pressure-test internal announcements before they send. Use when announcing a reorg, policy, or product change, drafting an all-hands or exec update, or deciding who hears what and in which order.

assets/announcement-template.md

View on GitHub
# Announcement Template

Fill every section. If a section does not apply, write why rather than deleting it —
deleted sections are how required elements go missing.

Target: under 500 words, reading grade 8-10, jargon density under 2%.
Verify with `scripts/announcement_auditor.py` before sending.

---

**Subject:** <the change and the date, not a teaser>

**Audience:** <who receives this>
**Channel:** <primary> | **Record:** <durable channel>
**Send date/time:** <not Friday, not the last hour of the day>

---

## What is changing

<One sentence. The change and the effective date. No preamble, no context first.>

> Example: From 1 September, expense approvals over $50 no longer need a manager signature.

## Why

<The actual reason, including the constraint that forced it. If the honest reason is cost,
say cost. Readers who suspect a hidden reason stop believing the rest of the message.>

## Who this affects

<Named groups.>

<Then, explicitly: "If you are not in these groups, nothing changes for you." Without this
sentence, every reader assumes it might be them.>

## What you need to do

<An action with a deadline, and how long it takes.>

<Or, in exactly these words: "No action needed.">

## What happens next

<Sequence and dates. What changes when. What is still being decided and when it will be.>

## Where to ask

<Named person or channel, plus a response commitment.>

> Example: Questions to #ask-finance. Priya answers within one business day.

---

## Pre-send checklist

- [ ] The change and date are in the first sentence
- [ ] The reason names a real constraint, not a strategy abstraction
- [ ] Unaffected people are told explicitly that they are unaffected
- [ ] There is an action with a deadline, or the words "no action needed"
- [ ] A named human owns questions, with a response time
- [ ] Managers were briefed first (or the message explains why they could not be)
- [ ] No feedback is invited on a decision that is already settled
- [ ] Auditor score is 75 or above
- [ ] Someone outside the working group read it and could restate the change accurately
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall