Foundation Stakeholder Briefings

Organization

product-on-purpose

foundation-stakeholder-briefings

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.

Overview

Publisher	product-on-purpose
Repository	`pm-skills`
Skill name	`foundation-stakeholder-briefings`
Stars	717
Forks	92
Bundled files	6
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by product-on-purpose on GitHub. Read the source before you install it.

Installation

Install the Foundation Stakeholder Briefings AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/product-on-purpose/pm-skills/tree/main/skills/foundation-stakeholder-briefings
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/product-on-purpose/pm-skills/tree/main/skills/foundation-stakeholder-briefings

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p .claude/skills
cp -r /tmp/pm-skills/skills/foundation-stakeholder-briefings .claude/skills/foundation-stakeholder-briefings

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Foundation Stakeholder Briefings in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Foundation Stakeholder Briefings on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Foundation Stakeholder Briefings is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

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
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

One async update of meeting outcomes for stakeholders. Use foundation-stakeholder-update (it is meeting-bound; that is its scope).
Understanding or mapping stakeholders (influence, interest, comms plan). Use discover-stakeholder-summary.
A persona to design or market against. Use foundation-persona.
There is no source content yet. This skill projects an existing artifact; it does not do the underlying analysis.

Instructions

When asked to create stakeholder briefings, follow these steps:

Ingest and classify the source. Read the provided artifact. Classify its type (spec/PRD, discovery/research, GTM/launch, strategy/roadmap, experiment/metrics, incident/retro, compliance/privacy/security, or raw/ambiguous). If the source is thin, continue but set input_quality: low and name the gap.
Build the master. Write the audience-neutral canonical document with these sections: What and Why, Decisions, Status, Risks and Open Questions, Asks, Timeline. Number every load-bearing claim with a stable ID (M1, M2, ...). The master carries no audience-specific spin; it is the shared substrate.
Propose the audiences. From the source type, propose the relevant subset using references/source-type-map.md (for example, a spec proposes Engineering, UX/Design, Data/BI, Executive; a GTM plan proposes PMM, Sales, CS/Support, Executive). Present the proposal and accept go (generate the proposed set), an edit (drop X, add Y), or all (all nine). If invoked with --go, skip the prompt and generate the proposal. No audience is ever locked out.
Project each briefing. For each chosen lens (see references/audience-lenses.md), render a self-contained block delimited by --- BEGIN: <lens> --- / --- END ---, containing:
- Draws on: the master claim IDs this briefing projects (required).
- Primary ask: exactly one decision or action for this audience (required).
- a one-line headline, a "what this means for you" framing, and the body, at the lens's length, vocabulary, and tone. Every load-bearing line must trace to a master claim. Do not introduce a claim that is not in the master.
Flag translations. Keep a translations-applied log (internal, below the shareable boundary) for every technical-to-business or inferred re-pitch, so the user can verify it lands. This section is never part of a shareable briefing.
Self-check the invariant before finalizing:
- Trace references resolve (deterministic, checkable): every briefing Draws on: ID resolves to a real master claim.
- One CTA (deterministic, checkable): exactly one Primary ask: per block.
- No untraced claim (review): re-read each block against its Draws on: set and confirm the body introduces nothing absent from those master claims. This is a review step, not automated.
- Neutral master (review): the master has no audience-specific spin. List anything that fails.
Render the artifact. Master (with claim IDs) -> the delimited briefing blocks -> the boundary marker -> the translations-applied log -> Sources and References. Remove all guidance blockquotes from the final output.

Audience lenses

Nine first-class lenses, each defined by the decision it owns, plus a Custom slot whose lens is inferred from the audience name and source and shown for confirmation. Full definitions, per-lens "not this lens when" boundaries, and the overlap matrix (Exec vs Board, PMM vs Sales, Engineering vs Data, Legal vs Exec) are in references/audience-lenses.md.

Output Format

A single artifact (filename YYYY-MM-DD_HH-MMtz_<title>_stakeholder-briefings.md), built from references/TEMPLATE.md.
Each briefing block is self-contained and send-ready (BEGIN/END cut-lines) so it can be copied out without edits.
A future --split mode (write each block to its own file) is deferred; v1 is single-artifact.

Quality Checklist

Master present with numbered claim IDs (M1, M2, ...) and no audience-specific spin.
Each briefing block has a Draws on: line whose IDs all resolve to master claims.
Each briefing block has exactly one Primary ask:.
No briefing asserts a claim absent from the master (projection rule).
Audience set matches the source-type proposal or the user's edit; N=1 honored without refusal.
Translations-applied log present (internal) when any translation was made; boundary marker separates shareable blocks from internal sections.
Each briefing is at the lens's length and tone (a board block reads nothing like an engineering block).
Guidance blockquotes removed from the final artifact.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Foundation Stakeholder Briefings AI skill do?

Why use Foundation Stakeholder Briefings on TypingMind?

Because you install it once and use it with any model. Foundation Stakeholder Briefings is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Foundation Stakeholder Briefings in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/product-on-purpose/pm-skills/tree/main/skills/foundation-stakeholder-briefings. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Foundation Stakeholder Briefings?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Foundation Stakeholder Briefings?

As many as you like. As long as a model supports skills, you can use Foundation Stakeholder Briefings with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Foundation Stakeholder Briefings AI skill free?

Yes. It is published on GitHub by product-on-purpose under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Testing

openclaw

OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar…

Deployment Patterns

Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones…

Docker Patterns

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

Foundation Stakeholder Briefings

Overview