internal-comms
Internal Communications
Document Types
Status Report
# [Project Name] Status Report
**Date:** [Date]
**Author:** [Name]
**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked
## Summary
[2-3 sentence overview]
## Progress This Week
- Completed: [items]
- In Progress: [items]
- Blocked: [items with owners]
## Key Metrics
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Metric] | [Target] | [Actual] | ⬆️/➡️/⬇️ |
## Next Week
- [Planned items]
## Risks & Mitigations
| Risk | Impact | Mitigation | Owner |
|------|--------|------------|-------|
| [Risk] | H/M/L | [Action] | [Name] |
## Asks
- [Any blockers needing escalation]
Leadership Update
# [Team] Update - [Date]
## TL;DR
[One paragraph executive summary - the only thing busy execs will read]
## Wins
- [Key accomplishment with impact]
- [Key accomplishment with impact]
## Challenges
- [Challenge]: [What we're doing about it]
## Key Decisions Needed
1. [Decision]: [Context, options, recommendation]
## Metrics Dashboard
[Include 3-5 key metrics with trends]
Incident Report
# Incident Report: [Title]
**Severity:** P0/P1/P2/P3
**Duration:** [Start] - [End]
**Impact:** [User/revenue impact]
**Status:** Resolved/Monitoring/Active
## Timeline
| Time (UTC) | Event |
|------------|-------|
| [Time] | [What happened] |
## Root Cause
[Clear explanation of what went wrong]
## Resolution
[What was done to fix it]
## Action Items
| Item | Owner | Due Date | Status |
|------|-------|----------|--------|
| [Action] | [Name] | [Date] | ⬜/✅ |
## Lessons Learned
- [What we learned]
- [What we'll do differently]
All-Hands Announcement
# [Announcement Title]
Hey team,
[Opening that sets context]
**What's happening:** [Clear, simple explanation]
**Why it matters:** [Impact and benefits]
**What you need to do:** [Specific actions if any]
**Timeline:**
- [Date]: [Milestone]
- [Date]: [Milestone]
**Questions?** [Where to ask]
[Sign-off]
Writing Principles
- Lead with the bottom line - Busy readers skim
- Be specific - Numbers > adjectives
- Own problems - "We missed" not "It was missed"
- Action-oriented - Every problem has a next step
- Appropriate tone - Match urgency to content
More from moodmnky-llc/mood-mnky-command
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. Use when the user asks to create a poster, piece of art, design, or other static visual piece. Creates original visual designs.
14code-refactoring
Code refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.
13changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
12llm-application-dev
Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration. Use for AI-powered features, chatbots, or LLM-based automation.
11javascript-typescript
JavaScript and TypeScript development with ES6+, Node.js, React, and modern web frameworks. Use for frontend, backend, or full-stack JavaScript/TypeScript projects.
11python-development
Modern Python development with Python 3.12+, Django, FastAPI, async patterns, and production best practices. Use for Python projects, APIs, data processing, or automation scripts.
11