# Foundation Stakeholder Briefings

Turns any source artifact (spec, discovery, research, GTM plan, experiment results...

- Repository: https://github.com/product-on-purpose/pm-skills (780 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add product-on-purpose/pm-skills --skill foundation-stakeholder-briefings -g -a claude-code -y`
Codex: `npx skills add product-on-purpose/pm-skills --skill foundation-stakeholder-briefings -g -a codex -y`
Cursor: `npx skills add product-on-purpose/pm-skills --skill foundation-stakeholder-briefings -g -a cursor -y`
Gemini CLI: `npx skills add product-on-purpose/pm-skills --skill foundation-stakeholder-briefings -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add product-on-purpose/pm-skills`

## Description

Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Use when one piece of work must reach several audiences who each need a different framing, decision, and level of detail.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
# Stakeholder Briefings

A stakeholder-briefings artifact takes one source (a PRD, a discovery synthesis, a research report, a GTM or launch plan, experiment results, a retro or incident write-up, or raw notes) and produces a single saveable file containing:

1. a **master document**: the canonical, audience-neutral synthesis of the work (what and why, decisions, status, risks and open questions, asks, timeline), with each claim numbered (`M1`, `M2`, ...); and
2. a set of **audience briefings**: the same content re-pitched for each chosen stakeholder, one self-contained, copy-paste-ready block per audience.

The skill runs **master-first, then projects**. The master is the single source of truth; every briefing is a projection of it. A briefing may omit, reorder, and translate master content, but it may never assert a claim that is not in the master. That projection rule is what keeps the executive version and the engineering version from quietly disagreeing, and it is the difference between this skill and asking a model to "rewrite this six ways."

Distinct from `foundation-stakeholder-update` (one async update of meeting outcomes for a single audience, meeting-bound), `discover-stakeholder-summary` (a map of who stakeholders are and their influence/interest), and `foundation-persona` (a customer/buyer viewpoint to design or market against).

## When to Use

- One piece of work must reach several audiences who each need a different framing, decision, and level of detail (a spec going to engineering, design, data, and the funder at once).
- You are about to manually rewrite the same update three to five ways, one per audience.
- A decision or result needs to propagate across functions without the versions drifting apart.
- A single audience needs a tailored briefing from a non-meeting source (N=1 is supported; the fan-out is the signature use, not a floor).

## When NOT to Use

The rest: https://github.com/product-on-purpose/pm-skills/blob/HEAD/skills/foundation-stakeholder-briefings/SKILL.md