foundation-stakeholder-briefings

Generates one canonical master document plus audience-tailored stakeholder briefings from a source artifact.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill foundation-stakeholder-briefings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundation-stakeholder-briefings
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/foundation-stakeholder-briefings
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill foundation-stakeholder-briefings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When one piece of work must reach several audiences, teams manually rewrite the same update three to five times, and the versions quietly drift apart. This Skill turns any source artifact into one canonical master document plus per-audience briefings that are traceable projections of the master, so the executive version and the engineering version never disagree.

Core Features & Use Cases

  • Master-first projection: Builds an audience-neutral master document with numbered claims (M1, M2, ...), then projects each briefing from it; no briefing may assert a claim absent from the master.
  • Nine audience lenses plus custom: Executive, Board, Engineering, UX/Design, PMM, Sales, CS/Support, Legal, and Data/BI, each defined by the decision it owns, with a Custom slot inferred and confirmed for other audiences.
  • Source-type audience proposals: Classifies the source (spec, discovery, GTM, strategy, experiment, incident, compliance, raw notes) and proposes the relevant audience subset, accepting go, edits, or all.
  • Use Case: You have a PRD for a new feature that must go to engineering, design, data, legal, and an executive sponsor. Run the Skill on the PRD to get one master document plus five copy-paste-ready briefing blocks, each with its own headline, framing, and exactly one primary ask.

Quick Start

Take this PRD and generate stakeholder briefings for engineering, design, data, and our executive sponsor from one master document.

Frequently Asked Questions about foundation-stakeholder-briefings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create stakeholder briefings for multiple audiences from one document?

Provide the source artifact and the Skill builds an audience-neutral master document with numbered claims, then projects one self-contained briefing block per audience. Each block is delimited by BEGIN/END markers so it can be copied out and sent as-is.

What audiences can stakeholder briefings be tailored to?

Nine first-class lenses are supported: Executive, Board, Engineering, UX/Design, PMM, Sales, CS/Support, Legal, and Data/BI. A Custom slot covers other audiences by inferring a lens from the audience name and source, shown for confirmation before generating.

How does the skill keep different audience versions from contradicting each other?

Every briefing is a traceable projection of the master document. Each block lists the master claim IDs it draws on, and the projection rule forbids asserting any claim not present in the master, so versions cannot drift apart.

Can I generate a briefing for just one audience?

Yes, single-audience requests are fully supported. The fan-out to many audiences is the signature use, but the Skill honors N=1 and generates just the one requested briefing without refusal.

When should I not use stakeholder briefings?

Do not use it for a single async update of meeting outcomes (use foundation-stakeholder-update), for mapping stakeholder influence and interest (use discover-stakeholder-summary), or when no source content exists yet, since it projects an existing artifact rather than doing the underlying analysis.