# Internal Comms

> Creates internal communications including all-hands presentations, team announcements, project status updates, async memos, meeting agendas, and executive briefings. Use when crafting messages from leadership, team updates, or structured internal documents. Do NOT use for external-facing marketing or customer communications.

- Skill: `knuckles-team/internal-comms` (Agent Skill)
- Install (CLI): `npx skillmds@latest add knuckles-team/internal-comms`
- Raw SKILL.md: https://api.skillmd.com/api/skills/knuckles-team/internal-comms/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- License: MIT
- Author: Knuckles-Team (https://skillmd.com/u/knuckles-team)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/knuckles-team/internal-comms

---

# Internal Communications

Craft clear, purposeful internal communications that inform, align, and motivate teams across all formats and organizational levels.

---

## Communication Types

### 1. Announcements (Team / Company-wide)

**Purpose:** Inform the team of a change, launch, or decision.

**Structure:**
```
Subject: [Direct, informative headline — include the key fact]

[Opening — lead with the news, no preamble]

What's changing:
- [Specific change 1]
- [Specific change 2]

Why we're doing this:
[1–2 sentences on the rationale]

What this means for you:
[Concrete action items or impact for the recipient]

Timeline:
- [Date]: [Milestone]

Questions? [Point of contact / channel]
```

**Tone principles:**
- Lead with the news — don't bury it
- Be direct; assume a busy reader
- Include a clear next step or action
- Avoid corporate jargon ("leverage," "synergize," "circle back")

---

### 2. All-Hands / Town Hall Agendas

**Purpose:** Structured agenda for company or department-wide meetings.

**Structure:**
```
[Meeting Name] — [Date] — [Duration]

Agenda

0:00–0:05  Welcome & Logistics (Host)
0:05–0:20  Company/Team Update (Leader)
  - [Key metric or milestone]
  - [Strategic context]
0:20–0:35  [Department/Project Spotlight] (Owner)
0:35–0:50  Q&A — open questions
0:50–0:55  Announcements & Upcoming dates
0:55–1:00  Closing

Pre-submitted questions: [link to form or doc]
Recording will be shared at: [channel/location]
```

**Tips:**
- Keep Q&A time > 15 minutes for genuine engagement
- Collect questions anonymously in advance for psychological safety
- End with a concrete takeaway or call to action

---

### 3. Project Status Updates (Async Memo Format)

**Purpose:** Keep stakeholders informed without requiring a meeting.

**Structure:**
```
Project: [Name]  |  Date: [YYYY-MM-DD]  |  Status: 🟢 On Track / 🟡 At Risk / 🔴 Blocked

Summary (1–2 sentences):
[What is this project and where does it stand?]

Progress since last update:
- ✅ [Completed]
- ✅ [Completed]

This week / next milestone:
- 🔄 [In progress]
- 📅 [Upcoming — by what date?]

Blockers & risks:
- [Blocker + who owns resolution + ETA]

Decisions needed:
- [Decision + decision maker + by when]

Links: [Design doc] | [Tracker] | [Slack thread]
```

---

### 4. Executive Briefings / Decision Memos

**Purpose:** Inform decision-makers efficiently and get a decision.

**Structure (1–2 pages max):**
```
MEMO
To: [Decision maker(s)]
From: [Author]
Date: [Date]
Re: [Decision or topic]

SITUATION
[2–3 sentences: what is happening and why this matters now]

PROPOSAL
[What are you recommending? Be specific.]

OPTIONS CONSIDERED
Option A: [Description] — [Pros / Cons]
Option B: [Description] — [Pros / Cons]

RECOMMENDATION
[State the recommendation clearly: "We recommend Option A because..."]

RESOURCES REQUIRED
[Budget / headcount / time]

DECISION NEEDED BY
[Date — and why this date]
```

---

### 5. Meeting Follow-Ups & Action Items

**Purpose:** Document decisions and accountabilities after a meeting.

**Structure:**
```
Meeting: [Name] | Date: [Date] | Attendees: [Names]

Decisions made:
- [Decision 1]
- [Decision 2]

Action items:
| Action | Owner | Due Date |
|--------|-------|----------|
| [Task] | [Name] | [Date] |

Next meeting: [Date / time / link — or "none scheduled"]

Full notes: [link if applicable]
```

---

## General Writing Principles

- **One idea per sentence** — if the sentence has "and," consider splitting it
- **Active voice** — "The team shipped X" not "X was shipped by the team"
- **Concrete details** — dates, numbers, names beat vague generalities
- **Know your audience** — executives need 1 page; teams need bullet points; ICs need context
- **End with a clear next step** — every message should answer "what do I do with this?"