foundation-stakeholder-update

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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

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

利益相关者更新是面向需要了解会议成果的读者的异步沟通内容。主要受众为未参会人员；次要受众是需要参考版本的部分参会人员（如迟到、中途离场、需要转发内容的人）。

与

/meeting-recap

（会议回顾）在受众、格式和用途上有所区别：会议回顾是为参会人员总结会议发生的内容；而利益相关者更新则是将会议成果转化为读者易懂的“对我意味着什么”的语言（根据读者角色定制，针对受众需求进行技术术语到业务语言的转换）。

与

/discover-stakeholder-summary

（利益相关者概况分析）也不同：该技能是关于了解利益相关者（作为用户工作的输入），而本技能是关于与利益相关者沟通（作为用户工作的输出）。

本技能属于会议技能家族，符合《会议技能家族协议》Meeting Skills Family Contract。

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

当会议成果影响未参会团队时，会后使用
当决策或承诺需要异步传达给下游团队时
已有会议回顾，需要将其转化为特定受众的语言时
用户需要向读者提出明确要求（特定CTA），且不能让该要求被忽略时

When NOT to Use

不适用场景

Summarizing what happened for attendees. Use
```
/meeting-recap
```
.
Broadcasting status with no specific audience tailoring. A plain Slack message is sufficient; the skill adds value when translation or CTA framing matters.
Communicating research findings to stakeholders. Use
```
/discover-interview-synthesis
```
plus targeted comms.

为参会人员总结会议内容：请使用
```
/meeting-recap
```
。
无特定受众定制的状态播报：普通Slack消息即可满足需求；只有当需要进行内容转换或CTA框架设计时，本技能才能发挥价值。
向利益相关者传达研究成果：请使用
```
/discover-interview-synthesis
```
（访谈综合分析）加上针对性沟通内容。

Zero-friction execution

零摩擦执行流程

Per the family contract, this skill never blocks on interrogation. Default flow:

Load related recap (preferred) or raw meeting notes
Detect thread continuation by scanning same directory for prior stakeholder-updates on the same
```
project
```
/
```
topics
```
Infer channel (if not specified) from audience variant: engineering / design → slack; leadership → email; mixed → notion
Present a brief inference summary (detected channel, audience, CTA, thread continuation if any, translation candidates)
Accept
```
go
```
or corrections
Produce the channel-tailored update

If invoked with

--go

, skip the inference summary. The entire output is shareable content (per family contract. no separate summary block needed).

根据家族协议，本技能绝不会因询问而中断执行。默认流程：

加载相关的会议回顾（优先选择）或原始会议记录
通过扫描同一目录中针对相同
```
project
```
/
```
topics
```
的过往利益相关者更新内容，检测线程延续性
根据受众变体推断渠道（若未指定）：工程/设计团队→Slack；管理层→邮件；混合受众→Notion
展示简短的推断总结（检测到的渠道、受众、CTA、线程延续状态（如有）、候选翻译内容）
接受
```
go
```
指令或修改意见
生成适配对应渠道的更新内容

若使用

--go

参数调用，则跳过推断总结环节。整个输出内容均可直接分享（符合家族协议，无需单独的总结块）。

Instructions

操作步骤

When asked to create a stakeholder update, follow these steps:

Load related recap Parse frontmatter to extract meeting context, decisions, actions, outcomes. If no recap provided, accept raw meeting notes with a lower input-quality flag.
Detect thread continuation Scan same directory for prior
```
stakeholder-update
```
artifacts with matching
```
project
```
/
```
topics
```
. If found, reference the prior update in the frontmatter
```
thread_continuation_of
```
field.
Present go-mode inference summary Show inferred channel (if not specified), detected audience, proposed CTA, thread continuation status, translation candidates (flagged jargon or acronyms that may not land).
Distill key outcomes From the recap or notes, select 3-5 outcomes that matter to the target audience. Do not include everything from the recap. filter by audience relevance.
Frame the CTA If action is needed: lead with it, not bury it If FYI-only: state explicitly in the TL;DR
Translate technical-to-business Flag jargon and acronyms unlikely to land with the audience. Provide plainer alternatives. Keep a translations-applied log for user verification in the output's Generation context.
Build the channel-tailored variant
- Slack / Teams: headline (one action-oriented line, optionally one emoji), TL;DR 3 bullets, context sentence, "what this means for [audience]", CTA (bold with marker if action needed; italic "FYI-only" if not), thread-continuation link, more-links footer
- Email: subject line (topic + outcome), greeting ("Hi [audience]"), opening sentence (headline + why they are receiving this), TL;DR, context 2-3 sentences, what was decided / advanced, what this means for your team, what I need from you (with by-when), thread reference, sign-off
- Notion: rich H1/H2/H3 structure, longer context block, collapsible sections for detail, table for decisions and actions
- Exec-memo: TL;DR first (3-4 lines), supporting detail in 3 sections max, asks section upfront, formal tone, no emoji
Render TEMPLATE.md with the selected variant as primary Other variants may be included as collapsible alternates for user flexibility. Remove all guidance blockquotes from the final artifact.
Validate
- ```
channel
```
  is in enum
- ```
audience_variant
```
  is in enum
- ```
primary_cta
```
  is non-empty (use "FYI-only" if no action needed)
- ```
related_recap
```
  is a valid filename reference or flagged as raw-notes input

当被要求创建利益相关者更新内容时，请遵循以下步骤：

加载相关会议回顾 解析前置元数据以提取会议背景、决策、行动项和成果。若未提供会议回顾，则接受原始会议记录并标记输入质量较低。
检测线程延续性 扫描同一目录中具有匹配
```
project
```
/
```
topics
```
的过往
```
stakeholder-update
```
文件。若找到，则在前置元数据的
```
thread_continuation_of
```
字段中引用该过往更新。
展示go模式推断总结 显示推断的渠道（若未指定）、检测到的受众、提议的CTA、线程延续状态、候选翻译内容（标记可能不被受众理解的行话或缩写）。
提炼核心成果 从会议回顾或记录中，选择3-5个对目标受众重要的成果。无需包含会议回顾中的所有内容，需根据受众相关性进行筛选。
构建CTA框架 若需要行动：将CTA放在开头，而非隐藏在内容中若仅为告知：在TL;DR（摘要）中明确说明
技术术语转业务语言 标记受众可能难以理解的行话和缩写，提供更通俗易懂的替代表述。在输出的生成上下文（Generation context）中保留翻译日志，供用户验证。
构建适配渠道的变体内容
- Slack / Teams：标题（一句面向行动的表述，可搭配一个表情）、TL;DR（3个要点）、背景说明句、“对[受众]的影响”、CTA（若需行动则加粗标记；若仅为告知则用斜体标注“FYI-only”）、线程延续链接、更多链接页脚
- 邮件：主题（主题+成果）、问候语（“您好[受众]”）、开头句（标题+接收原因）、TL;DR、2-3句背景说明、已做出的决策/推进的事项、对您团队的影响、我需要您做什么（含截止时间）、线程参考、落款
- Notion：丰富的H1/H2/H3结构、较长的背景块、可折叠的细节部分、决策与行动项表格
- 高管备忘录：先放TL;DR（3-4行）、最多3个部分的支持细节、前置需求部分、正式语气、无表情
使用选定的变体作为主要内容渲染TEMPLATE.md 可将其他变体作为可折叠的备选内容包含在内，提升用户灵活性。从最终文件中移除所有指导性引用块。
验证
- ```
channel
```
  属于枚举值
- ```
audience_variant
```
  属于枚举值
- ```
primary_cta
```
  非空（若无需行动则使用“FYI-only”）
- ```
related_recap
```
  是有效的文件名引用或标记为原始记录输入

Quality checklist

质量检查清单

Channel variant matches the specified or inferred channel
Audience variant's "what this means for you" is specifically tailored (not generic)
CTA is surfaced up front, not buried
Technical-to-business translations are logged in Generation context for user verification (INTERNAL. outside shareable boundary)
Thread continuation referenced if prior updates exist on the same topic
```
## Shareable update
```
section present with channel-tailored body (v1.1.0. replaces "entire output is shareable" from v1.0.0)
Explicit boundary marker between Shareable update and internal sections (translations, sources)
Sources and References section lists the source recap and any prior updates in thread (INTERNAL)

Filename uses v1.1.0 variant pattern:

YYYY-MM-DD_HH-MMtimezone_title_stakeholder-update-{channel}-{audience}.md

渠道变体与指定或推断的渠道匹配
受众变体的“对您的影响”部分是针对性定制的（非通用内容）
CTA放在开头，未被隐藏
技术术语到业务语言的翻译已记录在生成上下文供用户验证（内部内容，不可分享）
若存在同一主题的过往更新，已引用线程延续性
存在
```
## 可分享更新
```
部分，包含适配渠道的正文内容（v1.1.0版本，替代v1.0.0版本中“整个输出均可分享”的规则）
可分享更新与内部部分（翻译内容、来源）之间有明确的边界标记
来源与参考部分列出了源会议回顾和线程中的所有过往更新（内部内容）

文件名采用v1.1.0版本的命名模式：

YYYY-MM-DD_HH-MMtimezone_title_stakeholder-update-{channel}-{audience}.md