| name | internal-comms |
| description | Craft internal company communications including status updates, newsletters, incident reports, FAQ responses, and leadership updates. Use when user needs to write internal communications, team updates, company announcements, 3P updates, incident reports, or any structured workplace communication. |
Internal Communications Skill
Craft various types of internal company communications using standardized formats.
Communication Types
3P Updates (Progress, Plans, Problems)
## Progress
- [What was accomplished this week]
- [Milestones hit, metrics moved]
## Plans
- [What we're working on next]
- [Target dates]
## Problems
- [Blockers and challenges]
- [What help is needed]
Company Newsletter
# [Company Name] Weekly Digest
**Date**: [Date]
## Highlights
[2-3 key wins or announcements]
## Team Spotlight
[Recognition or team news]
## What's Coming
[Upcoming events, deadlines, launches]
## Resources
[Links to important docs or announcements]
FAQ Response
**Q: [Question]**
A: [Clear, direct answer in 2-4 sentences]
For more information: [Link or contact]
Status Update
## Project: [Name]
**Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked
**Last Updated**: [Date]
### Summary
[1-2 sentence executive summary]
### Progress Since Last Update
- [Bullet points]
### Next Steps
- [What's happening next]
### Risks & Blockers
- [If any]
### Key Metrics
| Metric | Target | Current |
|--------|--------|---------|
Leadership Update
# [Quarter/Month] Update from [Leader Name]
**To**: [Audience]
## Headline
[Most important thing — 1 sentence]
## Context
[Why this matters — 2-3 sentences]
## What We're Doing
[Concrete actions — 3-5 bullets]
## What This Means for You
[Direct implications for the audience]
## Next Steps
[Timeline and owners]
Incident Report
## Incident Report: [Brief Description]
**Incident Date**: [Date]
**Severity**: P1 / P2 / P3
**Status**: Resolved / Ongoing
### Summary
[1-2 sentence summary of what happened]
### Timeline
| Time | Event |
|------|-------|
| HH:MM | [Event] |
### Root Cause
[What caused the incident]
### Impact
[Who/what was affected and how]
### Resolution
[What was done to fix it]
### Action Items
| Item | Owner | Due Date |
|------|-------|----------|
Tone Guidelines
- Be direct: Lead with the most important information
- Use plain language: Avoid jargon unless writing for a technical audience
- Be specific: Use numbers, dates, and concrete details
- Respect reader time: Shorter is better — cut anything that doesn't add value
- Active voice: "We shipped X" not "X was shipped"
For Unknown Formats
If the requested communication type doesn't match the templates above, ask the user:
- What's the purpose of this communication?
- Who is the audience?
- What format have you used before for this type of update?
- Is there an example you can share?
