weekly-update

You can automate weekly stakeholder updates by reading a completed weekly summary and memory preferences to format the update for Slack, email, or Notion. This skill drafts concise, audience-aware communication from existing notes.

The best way to convert a weekly summary into a product management update is to synthesize the completed summary into key outcomes, decisions, and progress. This skill formats the distilled information for external readers.

Yes, you need a completed weekly summary to generate a stakeholder communication. The skill requires reading the weekly summary and your memory preferences to format the update for the intended audience.

Yes, you can format your weekly progress report differently for managers and teams. The skill applies audience-aware formatting by adapting the update for Slack, email, Notion, or another configured delivery format.

A stakeholder-facing weekly update for product managers should include what changed, what is next, and what stakeholders need to know. This skill highlights important outcomes, decisions, and progress from the week.

Using a dedicated tool for stakeholder communication prevents rewriting the same information from scratch. This skill converts internal weekly summaries into clear, professional updates without manual formatting overhead.