foundation-stakeholder-update

Solid

Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership, customer-facing, mixed). Surfaces a primary CTA up front, flags technical-to-business translations for user verification, and detects thread continuation from prior updates.

AI & Automation 290 stars 40 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- 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 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](../../docs/reference/skill-families/meeting-skills-contract.md). ## When to Use - After a meeting with outcomes affecting teams who were not in the room - When a decision or commitment needs to propagate to downstream teams async - When a recap exists and needs to be translated into audience-specific language - When the user needs something from readers (specific CTA) and cannot afford for it to be buried ## When NOT to Use - Summarizing what happened for attendees. Use `foundation-meeting-recap`...

Details

Author
product-on-purpose
Repository
product-on-purpose/pm-skills
Created
5 months ago
Last Updated
yesterday
Language
JavaScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category