Internal Comms Document Writing

Problem

Internal documents often require different formats: a 3P update should be short and structured, a company newsletter needs a consistent tone, an FAQ needs direct answers, and a management update should focus on status, risks, and next steps. The issue is not merely “writing,” but not knowing which tone, fields, and boundaries apply to the current document type, which can lead to project status being written like a newsletter or FAQ answers becoming over-explained.

How the skill works

The skill treats internal communications as a type-driven workflow:

• Identify the communication type: progress/plan/problems, company newsletter, FAQ, status report, management update, project update, incident report, etc.
• Load the matching guide: such as examples/3p-updates.md, examples/company-newsletter.md, examples/faq-answers.md, or examples/general-comms.md.
• Follow the guide: formatting, tone, and content collection are defined by the specific file; if the type is unclear, it asks for clarification instead of inventing a template.

Boundaries

It is useful when the internal communication goal is clear, but it is not a substitute for missing facts. If the request lacks project progress, issues, owners, or deadlines, the model should still ask for context. The guides shape presentation, not source material.