---
name: internal-comms
description: "Write professional internal communications: status reports, 3P updates, and summaries."
whenToUse: "User asks to write a status report or weekly update"
---

# Skill: Internal Communications

## Description
Write professional internal communications for Microsoft PM context: status reports, 3P updates, weekly summaries, team newsletters, meeting recaps, and email drafts. Adapted from Anthropic's internal-comms skill for CharZ's team.

## When to Use
- User asks to write a status report or weekly update
- User asks to draft an email to leadership or team
- User asks for 3P updates (Progress, Plans, Problems)
- User asks for meeting recap or summary
- User asks to write any internal communication
- User says "帮我写个周报" or "写个update"

## Communication Types

### 1. 3P Update (Progress / Plans / Problems)
```
## 📊 [Team/Area] Weekly Update — [Date]

### ✅ Progress (What we shipped/achieved)
- [Metric improvement]: Describe quantified impact
- [Feature shipped]: What it does, who benefits
- [Milestone reached]: Context and significance

### 📋 Plans (What's coming next)
- [Next deliverable]: ETA, owner, dependencies
- [Investigation]: What we're exploring and why
- [Upcoming milestone]: Target date and criteria

### ⚠️ Problems (Blockers & risks)
- [Blocker]: Impact, mitigation, help needed
- [Risk]: Probability, impact, contingency plan
- [Dependency]: Who/what we're waiting on
```

### 2. Leadership Update
- **Keep it to 5-7 bullet points max**
- Lead with **impact and metrics**, not activities
- Use "So what?" test — every bullet should answer why leadership cares
- Include 1 clear ask if needed
- Tone: Confident, concise, data-backed

### 3. Team Newsletter / Announcement
- Lead with the most exciting news
- Include people shoutouts (builds culture)
- Keep sections scannable (headers, bullets, bold key info)
- End with clear action items or dates

### 4. Meeting Recap
```
## 📝 Meeting Recap: [Meeting Name] — [Date]

### Attendees
[List key attendees]

### Key Decisions
1. [Decision]: Rationale and owner
2. [Decision]: Impact and timeline

### Action Items
| Owner | Action | Due Date |
|-------|--------|----------|
| Name  | Task   | Date     |

### Open Questions
- [Question]: Who needs to answer, by when
```

### 5. Incident Report
- Timeline of events (UTC timestamps)
- Root cause analysis
- Customer impact (quantified)
- Mitigation steps taken
- Follow-up actions with owners and dates

## Style Guidelines for CharZ's Team
- **Language**: Mix Chinese and English naturally (Chinese for narrative, English for technical terms)
- **Tone**: Professional but not stiff — CharZ's team has a casual, friendly culture
- **Data first**: Always quantify impact when possible
- **Attribution**: Credit specific people by name
- **Brevity**: If it can be said in 3 bullets, don't use 5
- **Emoji**: Use sparingly for section headers, not in every sentence
