Internal Communications
Use This Skill When
- Writing progress, plans, and problems (3P) team updates
- Creating company-wide newsletters or announcements
- Responding to FAQs or common questions
- Drafting status reports for leadership
- Documenting project updates or milestones
- Writing incident reports or postmortems
- Any internal company communication requiring consistent format
When NOT to Use
- External communications (PR, customer-facing messaging)
- Marketing copy or promotional content
- Personal messages not following company standards
- Highly sensitive legal/compliance matters
Context: Communication Standards Maturity
Undeveloped: Inconsistent formats, unclear messaging, no structure.
Target: Follow company templates, consistent tone, clear structure for each communication type.
Optimized: Automated formatting, tone consistency checking, cross-team alignment.
Core Principle
Consistency builds clarity. Using standardized formats for internal comms ensures information is where people expect it, leadership gets the signals they need, and team alignment increases.
Instructions
Step 1: Identify Communication Type
Determine which category your communication falls into:
| Type |
Purpose |
Frequency |
Audience |
| 3P Update |
Progress, Plans, Problems |
Weekly |
Team + Manager |
| Company Newsletter |
Broad updates, announcements |
Monthly/Quarterly |
All-hands |
| FAQ Response |
Answer common questions |
As-needed |
Public/Team |
| Status Report |
Leadership summary |
Bi-weekly/Monthly |
Executives |
| Project Update |
Specific project progress |
As milestone reached |
Stakeholders |
| Incident Report |
Critical issue documentation |
Urgent + Postmortem |
Team + Leadership |
Step 2: Load Appropriate Template
Reference the company's guideline file:
3P Updates → examples/3p-updates.md
- Format: Progress, Plans, Problems
- Length: 3-5 paragraphs
- Frequency: Weekly Monday
Company Newsletters → examples/company-newsletter.md
- Format: Highlights, wins, upcoming events
- Length: 2-3 pages
- Audience: All employees
FAQ Responses → examples/faq-answers.md
- Format: Question + answer + context
- Length: Concise but complete
- Searchability: Important for discovery
General Communications → examples/general-comms.md
- Format: Flexible but structured
- Use when type doesn't match above
Step 3: Follow Template Structure
Example: 3P Update Template
# 3P Update: [Your Name/Team] — [Week of DATE]
## Progress ✅
- [Completed milestone 1] — [brief context]
- [Completed milestone 2] — [brief context]
- [Progress on major item] — [% complete or status]
*Key win this week*: [Highlight one significant achievement]
## Plans 📋
- [Next priority 1] — starting [date]
- [Next priority 2] — starting [date]
- [Blocking item] — need [resource] by [date]
*Key upcoming milestone*: [Major deliverable date]
## Problems ⚠️
- [Issue 1] — impact: [X], resolution timeline: [Y]
- [Issue 2] — impact: [X], resolution timeline: [Y]
*How to help*: We need [specific ask] to unblock progress
Example: Company Newsletter Template
# Company Newsletter — [Month/Date]
## 🎉 This Month's Highlights
### Major Wins
- [Achievement 1] — [brief context]
- [Achievement 2] — [brief context]
### Customer Stories
- [Customer success 1]
- [Customer success 2]
## 📢 Announcements
### [Category]: [Announcement Title]
[Details and context]
### [Category]: [Announcement Title]
[Details and context]
## 🗓️ Upcoming Events
- [Event 1] — [date/time]
- [Event 2] — [date/time]
## 💡 Spotlight: [Team or Person]
[Recognition and context]
## 📊 By The Numbers
- [Metric 1]: [Value]
- [Metric 2]: [Value]
Step 4: Gather Required Information
Before drafting, collect:
| Communication Type |
Key Info Needed |
| 3P Update |
Last week's progress, current blockers, next week's priorities |
| Newsletter |
Wins from team, announcements, events, metrics |
| FAQ |
Common question, answer options, context |
| Status Report |
Metrics, milestones, risks, budget status |
| Project Update |
Current status, next steps, dependencies |
| Incident Report |
Timeline, impact, root cause, prevention |
Step 5: Draft Following Guidelines
Tone guidelines by communication type:
- 3P Update: Direct, factual, concise (assume reader is busy)
- Newsletter: Warm, celebratory, engaging (build community feeling)
- FAQ: Clear, helpful, jargon-minimized (assume reader is new)
- Status Report: Professional, metrics-driven, executive-level summary
- Project Update: Technical but accessible, clear next steps
- Incident Report: Objective, blameless, focus on learning
Step 6: Quality Checklist
Before sending:
Output
Deliver:
- Draft communication using appropriate template
- Tone verification (consistent with type)
- Completeness check (all required info included)
- Ready-to-send version formatted per company standards
1---2name: internal-comms3description: Write consistent, high-quality internal communications (status reports, 3P updates, newsletters, FAQs, incident reports). Use company standards and formats for all internal messaging.4---56# Internal Communications78## Use This Skill When910- Writing progress, plans, and problems (3P) team updates11- Creating company-wide newsletters or announcements12- Responding to FAQs or common questions13- Drafting status reports for leadership14- Documenting project updates or milestones15- Writing incident reports or postmortems16- Any internal company communication requiring consistent format1718## When NOT to Use1920- External communications (PR, customer-facing messaging)21- Marketing copy or promotional content22- Personal messages not following company standards23- Highly sensitive legal/compliance matters2425## Context: Communication Standards Maturity2627**Undeveloped**: Inconsistent formats, unclear messaging, no structure.2829**Target**: Follow company templates, consistent tone, clear structure for each communication type.3031**Optimized**: Automated formatting, tone consistency checking, cross-team alignment.3233## Core Principle3435**Consistency builds clarity.** Using standardized formats for internal comms ensures information is where people expect it, leadership gets the signals they need, and team alignment increases.3637## Instructions3839### Step 1: Identify Communication Type4041**Determine which category your communication falls into:**4243| Type | Purpose | Frequency | Audience |44|------|---------|-----------|----------|45| **3P Update** | Progress, Plans, Problems | Weekly | Team + Manager |46| **Company Newsletter** | Broad updates, announcements | Monthly/Quarterly | All-hands |47| **FAQ Response** | Answer common questions | As-needed | Public/Team |48| **Status Report** | Leadership summary | Bi-weekly/Monthly | Executives |49| **Project Update** | Specific project progress | As milestone reached | Stakeholders |50| **Incident Report** | Critical issue documentation | Urgent + Postmortem | Team + Leadership |5152### Step 2: Load Appropriate Template5354**Reference the company's guideline file:**5556- **3P Updates** → `examples/3p-updates.md`57 - Format: Progress, Plans, Problems58 - Length: 3-5 paragraphs59 - Frequency: Weekly Monday6061- **Company Newsletters** → `examples/company-newsletter.md`62 - Format: Highlights, wins, upcoming events63 - Length: 2-3 pages64 - Audience: All employees6566- **FAQ Responses** → `examples/faq-answers.md`67 - Format: Question + answer + context68 - Length: Concise but complete69 - Searchability: Important for discovery7071- **General Communications** → `examples/general-comms.md`72 - Format: Flexible but structured73 - Use when type doesn't match above7475### Step 3: Follow Template Structure7677**Example: 3P Update Template**7879```markdown80# 3P Update: [Your Name/Team] — [Week of DATE]8182## Progress ✅83- [Completed milestone 1] — [brief context]84- [Completed milestone 2] — [brief context]85- [Progress on major item] — [% complete or status]8687*Key win this week*: [Highlight one significant achievement]8889## Plans 📋90- [Next priority 1] — starting [date]91- [Next priority 2] — starting [date]92- [Blocking item] — need [resource] by [date]9394*Key upcoming milestone*: [Major deliverable date]9596## Problems ⚠️97- [Issue 1] — impact: [X], resolution timeline: [Y]98- [Issue 2] — impact: [X], resolution timeline: [Y]99100*How to help*: We need [specific ask] to unblock progress101```102103**Example: Company Newsletter Template**104105```markdown106# Company Newsletter — [Month/Date]107108## 🎉 This Month's Highlights109110### Major Wins111- [Achievement 1] — [brief context]112- [Achievement 2] — [brief context]113114### Customer Stories115- [Customer success 1]116- [Customer success 2]117118## 📢 Announcements119120### [Category]: [Announcement Title]121[Details and context]122123### [Category]: [Announcement Title]124[Details and context]125126## 🗓️ Upcoming Events127- [Event 1] — [date/time]128- [Event 2] — [date/time]129130## 💡 Spotlight: [Team or Person]131[Recognition and context]132133## 📊 By The Numbers134- [Metric 1]: [Value]135- [Metric 2]: [Value]136```137138### Step 4: Gather Required Information139140**Before drafting, collect:**141142| Communication Type | Key Info Needed |143|-------------------|-----------------|144| **3P Update** | Last week's progress, current blockers, next week's priorities |145| **Newsletter** | Wins from team, announcements, events, metrics |146| **FAQ** | Common question, answer options, context |147| **Status Report** | Metrics, milestones, risks, budget status |148| **Project Update** | Current status, next steps, dependencies |149| **Incident Report** | Timeline, impact, root cause, prevention |150151### Step 5: Draft Following Guidelines152153**Tone guidelines by communication type:**154155- **3P Update**: Direct, factual, concise (assume reader is busy)156- **Newsletter**: Warm, celebratory, engaging (build community feeling)157- **FAQ**: Clear, helpful, jargon-minimized (assume reader is new)158- **Status Report**: Professional, metrics-driven, executive-level summary159- **Project Update**: Technical but accessible, clear next steps160- **Incident Report**: Objective, blameless, focus on learning161162### Step 6: Quality Checklist163164**Before sending:**165166- [ ] Matches company template structure167- [ ] Tone consistent with communication type168- [ ] Length appropriate (not overly verbose)169- [ ] All key info included, no critical gaps170- [ ] Names and dates spelled correctly171- [ ] Links working and formatting clean172- [ ] If sensitive, review with manager first173- [ ] Proofread for grammar/typos174175## Output176177**Deliver:**1781791. **Draft communication** using appropriate template1802. **Tone verification** (consistent with type)1813. **Completeness check** (all required info included)1824. **Ready-to-send version** formatted per company standards
manu14357