foundation-stakeholder-briefings

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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

利益相关者简报工具可将一份源文件（如PRD、调研总结、研究报告、GTM或发布计划、实验结果、复盘或事件报告、原始笔记）转化为一个可保存的文件，其中包含：

主文档：经过标准化处理、不受受众影响的工作内容总结（包括内容与背景、已做决策、当前状态、风险与待解决问题、诉求、时间线），每个核心观点都带有编号（
```
M1
```
、
```
M2
```
……）；
多份受众定制简报：针对每个选定利益相关者重新呈现的内容，每个受众对应一个独立的、可直接复制粘贴的模块。

该工具遵循先构建主文档，再衍生简报的流程。主文档是唯一的事实来源；每份简报都是主文档的衍生版本。简报可省略、重新排序或转化主文档内容，但绝不能提出主文档中未包含的观点。正是这一衍生规则确保了高管版与工程版内容不会出现隐性分歧，这也是该工具与直接让模型“将内容改写六种版本”的核心区别。

本工具与以下工具有所不同：

foundation-stakeholder-update

（针对单一受众的会议结果异步更新，仅限会议场景）、

discover-stakeholder-summary

（利益相关者及其影响力/关注度图谱）和

foundation-persona

（用于设计或营销的客户/买家视角）。

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

同一项工作需要触达多个受众，且每个受众需要不同的内容框架、决策点和细节程度（例如一份规格说明同时面向工程、设计、数据团队和出资人）。
你正准备手动将同一更新内容改写3-5个版本，分别面向不同受众。
某项决策或结果需要跨部门同步，且各版本内容不能出现偏差。
单一受众需要从非会议源文件获取定制简报（支持仅面向1个受众的场景；多受众分发是核心用法，但并非最低要求）。

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.

针对利益相关者的会议结果异步更新。请使用
```
foundation-stakeholder-update
```
（该工具仅限会议场景，这是其适用范围）。
了解或梳理利益相关者（影响力、关注度、沟通计划）。请使用
```
discover-stakeholder-summary
```
。
用于设计或营销的用户角色。请使用
```
foundation-persona
```
。
尚无源文件内容。本工具仅对现有文件进行衍生处理，不负责底层分析工作。

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.

当被要求创建利益相关者简报时，请遵循以下步骤：

接收并分类源文件：阅读提供的文件，对其类型进行分类（规格说明/PRD、调研/研究、GTM/发布、战略/路线图、实验/指标、事件/复盘、合规/隐私/安全或模糊原始内容）。如果源文件内容单薄，可继续处理，但需标记
```
input_quality: low
```
并说明缺失的内容。
构建主文档：撰写不受受众影响的标准化文档，包含以下章节：内容与背景、已做决策、当前状态、风险与待解决问题、诉求、时间线。为每个核心观点分配一个稳定的编号ID（
```
M1
```
、
```
M2
```
……）。主文档不包含任何针对特定受众的倾向，是所有简报的共享基础。
推荐受众范围：根据源文件类型，参考
```
references/source-type-map.md
```
推荐相关受众子集（例如，规格说明的推荐受众为工程团队、UX/设计团队、数据/BI团队、高管；GTM计划的推荐受众为PMM、销售、客户成功/支持团队、高管）。提交推荐方案，并接受
```
go
```
（生成推荐的受众简报）、编辑指令（
```
移除X，添加Y
```
）或
```
all
```
（生成全部9类受众的简报）。如果调用时带有
```
--go
```
参数，则跳过提示直接生成推荐方案。所有受众均可被选择，无锁定限制。
衍生每份简报：针对每个选定的视角（参考
```
references/audience-lenses.md
```
），生成一个独立模块，用
```
--- BEGIN: <视角> ---
```
/
```
--- END ---
```
作为分隔符，模块内容包含：
- ```
参考主文档内容:
```
  本简报衍生自主文档的哪些观点ID（必填）。
- 核心诉求: 针对该受众的唯一决策或行动要求（必填）。
- 一行标题、“对您的意义”框架，以及符合该视角篇幅、词汇和语气的正文内容。所有核心内容必须可追溯到主文档的观点。不得引入主文档中未包含的观点。
标记内容转化记录：当存在技术术语转商业表述或推断性内容调整时，保留一份内部的内容转化日志（位于可共享内容边界之下），以便用户验证内容传达效果。该部分绝不会出现在可共享的简报中。
最终检查核心规则：
- 追溯引用有效（可验证的确定性检查）：每份简报的
```
参考主文档内容:
```
  中的ID均对应主文档中真实存在的观点。
- 仅一个核心诉求（可验证的确定性检查）：每个模块仅有一个
```
核心诉求:
```
  。
- 无未追溯观点（人工审核）：对照
```
参考主文档内容:
```
  的集合重新阅读每个模块，确认正文未引入集合外的主文档观点。这是人工审核步骤，非自动化检查。
- 主文档中立（人工审核）：主文档无针对特定受众的倾向。列出所有不符合要求的内容。
生成最终文件：主文档（带观点ID）→ 分隔的简报模块 → 边界标记 → 内容转化日志 → 来源与参考资料。移除最终输出中的所有指导性引用块。

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

包含9类一级视角，每类视角由其负责的决策定义，此外还有一个自定义视角槽位，其视角将根据受众名称和源文件推断并供用户确认。完整定义、每类视角的“非适用场景”边界，以及视角重叠矩阵（高管vs董事会、PMMvs销售、工程vs数据、法务vs高管）请参考

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.

单个文件（文件名格式为

YYYY-MM-DD_HH-MMtz_<标题>_stakeholder-briefings.md

），基于

references/TEMPLATE.md

构建。

每个简报模块均为独立可发送的内容（带有BEGIN/END分割线），无需编辑即可直接复制使用。
未来计划推出的
```
--split
```
模式（将每个模块保存为单独文件）暂未实现；v1版本仅支持单文件输出。

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.

主文档已包含带编号的观点ID（
```
M1
```
、
```
M2
```
……），且无针对特定受众的倾向。
每个简报模块的
```
参考主文档内容:
```
中的ID均对应主文档中真实存在的观点。
每个简报模块仅有一个
```
核心诉求:
```
。
简报未提出主文档中未包含的观点（符合衍生规则）。
受众范围符合源文件类型的推荐方案或用户编辑要求；支持仅面向1个受众的场景，无拒绝情况。
当存在内容转化时，已保留内部的内容转化日志；边界标记已分隔可共享模块与内部内容。
每份简报的篇幅和语气符合对应视角的要求（董事会模块与工程模块的风格完全不同）。
最终文件已移除所有指导性引用块。