Internal Comms Document Writer

Problem

Internal communications often have a fixed audience: managers, teams, and project stakeholders. The practical issue is inconsistent formatting, tone that is too strong or too soft, and incomplete information collection. A 3P update can read like a generic weekly note, a company newsletter can sound like an ad hoc notice, and FAQ answers can lack consistency.

How It Works

The skill maps the communication type to an example guide:
- 3P updates: progress, plan, and issue-oriented team syncs
- Company newsletter: company-level announcements
- FAQ: normalized answers to common questions
- Status reports, management updates, project updates, incident reports: routed to fallback guides such as examples/general-comms.md

During drafting, it first classifies the request, then loads the corresponding file from the examples/ directory and follows that guide for structure, tone, and content collection. If the type is unclear, it asks for clarification instead of forcing a template.

Boundaries

It is best for drafting and normalizing internal communication text. It does not replace fact checking, approval workflows, or cross-team confirmation. For incident impact, management judgment, or externally visible statements, key conclusions and sensitive wording should be reviewed manually.