foundation-stakeholder-update
Turn meeting outcomes into focused async updates tailored to your audience's role and channel. This skill translates decisions and actions into what-it-means language for non-attendees, surfaces the primary ask upfront, and detects thread continuations from prior updates. Choose from Slack, Teams, email, Notion, or exec-memo variants.
Foundation Stakeholder Update creates role-tailored async communication from meeting outcomes for non-attendees across Slack, Teams, email, Notion, and exec-memo formats.
AI-generated summary based on this skill's SKILL.md
Install
product-on-purpose/pm-skills/foundation-stakeholder-update · repository language: JavaScript
git clone https://github.com/product-on-purpose/pm-skills
cp -r pm-skills/skills/foundation-stakeholder-update ~/.claude/skills/foundation-stakeholder-updatenpx skillfed install product-on-purpose/pm-skills/foundation-stakeholder-updateFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I turn meeting notes into a Slack message for non-attendees?
foundation-stakeholder-update translates your meeting outcomes into channel-specific variants. Paste your meeting notes, select Slack as your channel, and specify your audience role (e.g., engineering, product, leadership). The skill generates a concise message that surfaces the primary CTA upfront, explains what decisions mean for that team, and flags any action items—all in Slack's conversational tone.
What does foundation-stakeholder-update do with technical decisions?
foundation-stakeholder-update translates technical decisions into role-specific language for different audiences. If your meeting covered a backend architecture choice, it rewrites that for business stakeholders as business impact, for ops as deployment steps, and for executives as risk and timeline. Each translation keeps the core decision intact but speaks to what matters to that role.
Can foundation-stakeholder-update create async communication from meeting outcomes?
Yes. foundation-stakeholder-update is built to create tailored async communication from meeting outcomes for non-attendees. It detects who wasn't in the room, identifies the primary asks and decisions, and generates updates in your chosen format—Slack, Teams, email, Notion, or exec-memo—so people stay informed without attending.
How do I communicate meeting results to my team in different channels?
foundation-stakeholder-update generates channel-specific variants from a single meeting recap. Specify your target channel (Slack, Teams, email, Notion, or exec-memo) and audience role, and the skill adapts tone, length, and emphasis. Slack messages stay brief with emoji; emails are formal; Notion updates are structured; exec memos lead with impact.
Does foundation-stakeholder-update track prior updates?
foundation-stakeholder-update detects and references prior updates to maintain thread continuity. If you've sent earlier stakeholder communications on the same topic, the skill acknowledges them and shows how this meeting's outcomes build on or shift from previous decisions, keeping your narrative coherent across async touchpoints.
What makes foundation-stakeholder-update different from a meeting template?
foundation-stakeholder-update goes beyond templates by surfacing primary CTAs and action items upfront, translating jargon for each audience's role, and generating ready-to-send variants for five channels. It also maintains continuity with prior updates and ensures non-attendees get what-it-means context, not just raw notes.
SKILL.md
rendered from the published skill — quoted content, verbatim
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 5 files
skills/foundation-stakeholder-update/HISTORY.md
skills/foundation-stakeholder-update/SKILL.md
skills/foundation-stakeholder-update/evals/trigger-fixtures.json
skills/foundation-stakeholder-update/references/EXAMPLE.md
skills/foundation-stakeholder-update/references/TEMPLATE.md