Generate Internal Communications

Internal Comms is a skill for writing internal company communications using repeatable formats. It covers 3P updates (Progress, Plans, Problems), company newsletters, FAQ responses, status reports, leadership updates, project updates and incident reports. The skill works by identifying the communication type from the request, loading the matching guideline file from its examples directory, and then following the formatting, tone and content-gathering instructions in that file.

Four guideline files are bundled: one for 3P team updates, one for company-wide newsletters, one for answering frequently asked questions, and a general file for anything that does not match the other three. For other formats, the skill uses the audience and purpose you supply together with the general guide, and it asks only for missing information that materially changes the draft.

The 3P update is deliberately short. It should be readable in 30-60 seconds, aimed at executives, leadership and teammates who have some but not much context on what the team does. It covers one reporting period, almost always a week, in three sections: what the team accomplished, what it plans to do next, and what is slowing it down. Each section is one to three sentences, data-driven, and matter-of-fact in tone. The default format is:

[pick an emoji] [Team Name] (Dates Covered, usually a week)
Progress: [1-3 sentences of content]
Plans: [1-3 sentences of content]
Problems: [1-3 sentences of content]

The newsletter guideline targets roughly 20-25 bullet points that a whole company will read via Slack and email. It calls for many links, short one or two sentence bullets, and the "we" voice. It suggests grouping bullets into clusters such as product development, go to market and finance, or external news and internal news, and it says to scale the scope to the actual company size rather than assume an employee count. The FAQ guideline asks for the questions that confuse many employees, each with a one-sentence question and a one or two sentence answer.

Use it when you need a status report, leadership update, weekly 3P, newsletter, FAQ digest, project update or incident report and want a consistent structure. For a weekly 3P update, the skill's own example turns two confirmed shipped items, one next-week task and one open dependency into Progress, Plans and Problems, preserving dates and uncertainty and leaving unknown metrics out.

Do not treat a draft as a sent message. The skill states that drafting does not authorize sending, scheduling or publishing, and that the expected handoff is a draft for the intended audience, not a claim that a message went out. Use only the audience, date range and approved sources you were given. Read only relevant accessible material, and remember that reactions, executive seniority and document views are not proof of accuracy. A private source does not automatically belong in a company-wide update. The skill also says to use it only when the task clearly matches its scope, not to treat the output as a substitute for environment-specific validation or expert review, and to stop and ask when required inputs, permissions, safety boundaries or success criteria are missing.

Inputs are the communication type, the team name and time period for a 3P update, the intended audience and purpose, and the tone you want (formal, casual, urgent or informational) for anything handled by the general guide. Any specific formatting requirement should be confirmed up front. Where nothing else is supplied, the skill uses its default formats. The output is a draft communication in the chosen format, written for the stated audience.

The guideline files describe pulling material from workplace tools when they are available: Slack posts from team members and messages in large channels with many reactions, Google Drive documents written by key team members, emails with many responses, and calendar events such as product reviews or all-hands meetings. When you have no access to those tools, the skill asks you what you want covered and mostly formats it for you. Every source is bounded by permissions: the approved sources and audience take precedence over the template suggestions.

Anyone asked to write a 3P update, company newsletter, FAQ roundup, status report, leadership update, project update or incident report. It suits requests where the audience and purpose are known and a consistent, concise structure matters more than free-form prose.