Internal Comms Writer

Write internal communications using formats teams actually use. Adapted from Anthropic's internal-comms skill, with templates inlined so it works in a sandboxed container.

Identify the format

From the user's request, pick the matching template:

| Type | Use when |

|---|---|

| 3P Update | Weekly team status: Progress, Plans, Problems |

| Company Newsletter | Cross-org monthly/quarterly recap |

| Leadership Memo | Strategic decision or policy change |

| FAQ Response | Answer to a recurring question |

| Incident Report | Postmortem of an outage or mistake |

| Project Update | Milestone-based project status |

If unclear, ask before drafting.

Template — 3P Update

# <Team> Update — Week of <date>

## Progress (last week)
- <Outcome>, not activity. e.g. "Launched checkout v2; conversion up 4%"
- Include 1-2 numbers if possible.

## Plans (next week)
- Top 3-5 priorities. If you list more than 5, you don't have priorities.

## Problems / Asks
- What's blocked or needs help. Specific ask, named owner.
- If nothing, write "None this week" — don't invent problems.

Template — Leadership Memo

# <Decision title>

**TL;DR:** <One sentence with the decision.>

## Context
What changed. Why we're writing this now.

## Decision
What we are doing. Be specific. Include effective date.

## What this means for you
- <Group A>: <impact>
- <Group B>: <impact>

## What's NOT changing
Explicitly call this out — prevents rumor.

## Questions
Where/how to ask. Named owner.

Template — FAQ Response

**Q: <The exact question, verbatim>**

<2-4 sentence answer. Lead with the answer, then context.>

<If there's nuance: bullet list of when X applies vs when Y applies.>

Related: <links to docs / past memos>

Template — Incident Report

# Incident: <Short title> — <date>

**Severity:** <S0/S1/S2>  **Duration:** <X min>  **Impact:** <users/revenue affected>

## What happened
3-5 sentence narrative in plain English.

## Timeline (UTC)
- HH:MM — <event>
- HH:MM — <event>

## Root cause
The ACTUAL technical cause. Not "human error" — what did the human assume that turned out wrong?

## What went well
What detection / response worked.

## What went poorly
Gaps in monitoring, runbooks, or knowledge.

## Action items
- [ ] <Specific fix> — owner: <name> — by: <date>

Template — Company Newsletter

# <Company> — <Month YYYY>

## What we shipped
- <Feature> — what it does, who it helps. 1 sentence.

## Numbers that matter
- <Metric>: <value> (<delta vs last period>)

## Team
- Welcome: <new hires>
- Moves: <internal moves, promotions>

## Coming up
- <Major dates next period>

Voice rules for all formats

• Lead with the conclusion or the action.
• One idea per paragraph.
• Cut hedges ("we think maybe", "it's probably").
• Numbers > adjectives (not "huge improvement" — "+22% week over week").
• No mystery: name owners, dates, exact systems.

Process

1. Confirm the format and audience.
2. Ask for any raw input the user has (notes, log lines, metrics).
3. Fill the template.
4. Self-edit pass: cut filler, check the voice rules, check every claim is specific.
5. Show the user a preview before they send.