foundation-meeting-brief

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Meeting Brief

会议简报

A meeting brief is the user's private strategic preparation document for a meeting where context, stakes, or positioning matter. It captures what the user needs to know, what they want to accomplish, who they are engaging with, and how to navigate the conversation. This is strategic prep, not meeting structure, which keeps it distinct from a meeting agenda.

This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.

会议简报是用户在涉及背景、利害关系或立场定位的会议前使用的私人战略准备文档。它记录了用户需要了解的信息、想要达成的目标、沟通对象以及如何引导对话。这是战略准备材料，而非会议结构安排，因此与会议议程有所区别。

本技能属于会议技能家族，符合会议技能家族协议。

When to Use

使用场景

Walking into a stakeholder review, exec briefing, or negotiation-adjacent conversation
First meeting with a new stakeholder where relationship calibration matters
A meeting where the user needs something from others (capacity commitment, decision, approval)
Any conversation where specific positioning, messaging, or risk navigation is required

参与利益相关者评审、高管简报或类谈判对话时
与新利益相关者首次会面，且关系校准至关重要时
用户需要从他人处获取资源（产能承诺、决策、批准）的会议
任何需要特定立场定位、信息传递或风险管控的对话

When NOT to Use

不适用场景

Preparing the agenda attendees will see. Use
```
/meeting-agenda
```
instead.
Post-meeting summarization. Use
```
/meeting-recap
```
.
The meeting is low-stakes and well-trodden (recurring team sync, standup). A brief is overhead for these; the agenda alone is sufficient.

准备参会者可见的议程时，请使用
```
/meeting-agenda
```
会议总结时，请使用
```
/meeting-recap
```
低风险且流程固定的会议（如 recurring team sync、站会）。此类会议使用简报属于冗余操作，仅议程即可满足需求。

Zero-friction execution

零摩擦执行

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

Read all provided inputs (topic, attendees, prior recaps, stakeholder summaries, user's primary ask)
Auto-discover related artifacts via
```
project
```
or
```
topics
```
frontmatter match
Run inference on missing values (stakeholder positions from prior recaps, primary ask from topic, top-3 goals from meeting type)
Present a brief inference summary and accept one-word
```
go
```
or corrections
Produce the brief

If invoked with

--go

, skip the inference summary. If the user provides all values upfront, no checkpoint appears.

The skill runs on inferred stakeholder positions with low-confidence flags when no stakeholder summaries are provided; it does not block on missing inputs.

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

读取所有提供的输入信息（主题、参会者、过往总结、利益相关者摘要、用户核心诉求）
通过
```
project
```
或
```
topics
```
前置匹配自动发现相关文档
对缺失值进行推断（从过往总结中推断利益相关者立场、从主题推断核心诉求、从会议类型推断Top 3目标）
展示简要推断总结，并接受单字指令
```
go
```
或修改意见
生成简报

若调用时附带

--go

参数，则跳过推断总结环节。若用户提前提供所有必要信息，则不会出现检查点。

当未提供利益相关者摘要时，技能会基于低置信度标记的推断立场运行，不会因缺失输入而中断。

Anti-meeting check

反会议检查

This skill opens with the shared anti-meeting check. see

/meeting-agenda

for the full check.

v1.1.0: the check requires a positive synchronous-value statement (tradeoff to discuss, conflict to resolve, co-creation, relationship-building, or blocker escalation). Brief-prep scenarios most often pass because they typically involve navigating stakeholder positions or negotiation dynamics. which qualify as "conflict to resolve" or "relationship-building." But the check still runs, and if no synchronous value is named, the skill recommends the async alternative before producing a brief.

Load-bearing inference gates (v1.1.0): when stakeholder positions, primary ask, or decision-maker attribution are inferred below-high confidence, flag in the go-mode summary with

⚠

. The brief's tactical guidance depends on these; silent acceptance of weak inferences creates risky advice. See family contract "Zero-friction execution" section.

本技能会先执行共享的反会议检查。完整检查内容请参见

/meeting-agenda

。

v1.1.0版本：检查要求明确的同步价值声明（需讨论的权衡、需解决的冲突、共创、关系建立或障碍升级）。简报准备场景大多能通过检查，因为这类场景通常涉及引导利益相关者立场或谈判动态，符合“需解决的冲突”或“关系建立”范畴。但检查仍会执行，若未明确同步价值，技能会在生成简报前建议异步替代方案。

承载性推断关卡（v1.1.0版本）：当利益相关者立场、核心诉求或决策者归属的推断置信度低于高置信度时，会在go模式总结中用

⚠

标记。简报的战术指导依赖这些信息；默认接受低置信度推断会产生高风险建议。详情请见家族协议的“零摩擦执行”章节。

Instructions

操作步骤

When asked to create a meeting brief, follow these steps:

Run anti-meeting check Apply the trigger patterns. If matched, propose async alternative and await override.
Parse and load inputs Read the topic. Load any
```
@file
```
references. Auto-discover related artifacts: prior recaps on same topic (same
```
project
```
/
```
topics
```
frontmatter), stakeholder summaries from
```
/discover-stakeholder-summary
```
outputs, related project docs.

Infer missing values Apply these rules:

Value	Inferred from	Confidence
Stakeholder positions	Prior recap language, stakeholder summary content	High if recap cites direct quote; medium if position in 2+ sources; low otherwise
Stakes per attendee	Role plus topic-ownership cues	Always flag inferences
Top 3 goals	User's primary ask plus meeting type	Offer as ranked strawman in go-mode
Anticipated questions	Stakeholder position analysis plus typical-by-role objections	Flag as inferred
Risks / tensions	Conflict patterns in prior recaps	High if prior recap flagged contradiction

Present go-mode inference summary Show the inferred stakeholder positions, primary ask, top-3 goals. Accept
```
go
```
or corrections.
Build the background section Relevant history, prior decisions, recent developments. Cross-reference prior recaps by filename when available.
Do per-stakeholder analysis For each key attendee: position on topic, stakes (what they win or lose), likely concerns, relationship state (strong / neutral / strained), tactical notes (how to engage).
Rank desired outcomes Must achieve / should achieve / nice to achieve. Force the tradeoff explicitly.
Draft key messages In priority order, phrased for delivery. Not bullet points to read; phrased as you would say them.
Anticipate questions and responses Table format: Q | prepared response. Aim for the three questions the user is most likely to get.
Identify risks and tensions With explicit mitigations. Flag anything that could derail the meeting.
Specify asks What the user needs from specific people by name. Not generic "get alignment" but "ask alex to commit eng capacity for Q2 by Thursday."
Define success signals How the user knows in the moment that the meeting went well. Behavioral cues, not just outcome markers.
Render TEMPLATE.md and validate
- ```
visibility: private
```
  default
- Stakeholder list has minimum fields (name, position) when present
- Primary ask is non-empty (use "alignment" or "information gathering" if no specific ask)

当被要求创建会议简报时，请遵循以下步骤：

执行反会议检查 应用触发模式。若匹配，提出异步替代方案并等待用户覆盖指令。
解析并加载输入信息 读取主题。加载所有
```
@file
```
引用。自动发现相关文档：同一主题的过往总结（相同
```
project
```
/
```
topics
```
前置信息）、
```
/discover-stakeholder-summary
```
输出的利益相关者摘要、相关项目文档。

推断缺失值 应用以下规则：

字段	推断来源	置信度
利益相关者立场	过往总结表述、利益相关者摘要内容	若总结引用直接引述则为高置信度；若立场来自2个以上来源则为中置信度；否则为低置信度
每位参会者的利害关系	角色及主题主导线索	所有推断均需标记
Top 3目标	用户核心诉求及会议类型	在go模式中作为排序后的草案提供
预期问题	利益相关者立场分析及典型角色异议	标记为推断内容
风险/矛盾点	过往总结中的冲突模式	若过往总结标记过矛盾则为高置信度

展示go模式推断总结 展示推断出的利益相关者立场、核心诉求、Top 3目标。接受
```
go
```
指令或修改意见。
构建背景部分 相关历史信息、过往决策、最新进展。若有可用文件，通过文件名交叉引用过往总结。
进行逐利益相关者分析 针对每位关键参会者：对主题的立场、利害关系（得失）、潜在顾虑、关系状态（良好/中立/紧张）、战术提示（沟通方式）。
排序期望结果 分为必须达成/应该达成/可达成三类。明确要求进行权衡取舍。
草拟关键信息 按优先级排序，以口语化表述呈现，而非用于朗读的项目符号。
预判问题与回复 表格格式：问题 | 预设回复。目标是覆盖用户最可能遇到的三个问题。
识别风险与矛盾点 附带明确的缓解措施。标记任何可能破坏会议进程的因素。
明确具体诉求 用户需要向特定人员提出的具体请求，而非泛泛的“达成共识”，例如“要求Alex在周四前承诺Q2的工程产能”。
定义成功信号 用户如何在会议过程中判断会议进展顺利。关注行为线索，而非仅结果指标。
渲染TEMPLATE.md并验证
- 默认设置
```
visibility: private
```
- 若存在利益相关者列表，需包含最少字段（姓名、职位）
- 核心诉求不能为空（若无具体诉求，使用“达成共识”或“信息收集”）

Quality checklist

质量检查清单

Anti-meeting check was applied and recorded
```
visibility: private
```
default applied
Background section cross-references prior recaps when available
Every key stakeholder has a position, stakes, concerns, relationship state entry (with confidence markers on inferred fields)
Desired outcomes are ranked (must / should / nice), not flat
Key messages are phrased for delivery, not for reading
Anticipated Q&A table has 3 or more entries
Asks are specific (named person, specific ask, by-when)
Shareable summary suitable for trusted-advisor review only (flagged as such)
Sources and References section includes Generation context with inferences flagged

已执行并记录反会议检查
已应用默认的
```
visibility: private
```
设置
背景部分已交叉引用可用的过往总结
每位关键利益相关者均有立场、利害关系、顾虑、关系状态记录（推断字段需标记置信度）
期望结果已排序（必须/应该/可达成），而非平铺罗列
关键信息以口语化表述呈现，而非书面化朗读内容
预期问答表格包含3项及以上内容
诉求具体明确（指定人员、具体请求、截止时间）
可共享摘要仅适合可信顾问审阅（需标记）
来源与参考部分包含生成上下文，并标记推断内容

另请参阅

Meeting Skills Family Contract
```
/meeting-agenda
```
. shares the anti-meeting check
```
/discover-stakeholder-summary
```
. upstream input source for stakeholder positions

会议技能家族协议
```
/meeting-agenda
```
：共享反会议检查
```
/discover-stakeholder-summary
```
：利益相关者立场的上游输入来源