Foundation Stakeholder Update

Use this when a meeting's outcomes need to reach people who weren't in the room and the message has to land differently for each reader. It takes a recap or raw notes and produces a channel-specific update (Slack, Teams, email, Notion, or an exec memo) tailored to an audience like engineering, leadership, or customer-facing staff. The useful parts are the primary call-to-action pulled to the top, a log of jargon it translated into plainer terms so you can check those yourself, and automatic linking to earlier updates on the same topic. It's not a replacement for the meeting recap, which is for attendees. The main caveat is that its technical-to-business translations are a best guess, so read those before you send.

skills.sh installs: 742
GitHub stars: 794
last updated: Aug 4, 2026

View on GitHub

Install

$ npx -y skills add product-on-purpose/pm-skills --skill foundation-stakeholder-update --agent claude-code

Installs into .claude/skills of the current project.

Files

Stakeholder Update

A stakeholder update is async communication to readers who need to know the outcomes of a meeting. Primary audience is non-attendees; secondary audience is some attendees who want a reference version (came in late, stepped out, need something to forward).

Distinct from foundation-meeting-recap in audience, format, and purpose: the recap is a summary of what happened for people who were in the room; the stakeholder-update is a translation of outcomes into what-it-means for readers (tailored to their role, with technical-to-business translation where the audience warrants it).

Distinct from /discover-stakeholder-summary: that skill is about understanding stakeholders (input to the user's work). This skill is about communicating to stakeholders (output from the user's work).

This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.