foundation-meeting-agenda

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Meeting Agenda

会议议程

A meeting agenda is the attendee-facing structural document that sets expectations before a meeting. It answers "what will we discuss, who owns each topic, how will we spend the time, and what does done look like?" Distinct from a meeting brief, which is the user's private strategic prep; the agenda is shared with participants and focused on structure and flow.

This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract, which defines shared frontmatter, file naming, the go-mode behavioral pattern, and universal output requirements across all meeting skills.

会议议程是面向参会者的结构性文档，用于在会前明确预期。它回答了“我们将讨论什么、各议题由谁负责、时间如何分配，以及达成目标的标准是什么？”的问题。与作为用户私人战略准备材料的meeting brief不同，议程会与参会者共享，重点关注会议的结构与流程。

本Skill属于会议Skills家族，符合《会议Skills家族协议》的规范，该协议定义了所有会议Skills通用的前置内容、文件命名规则、go-mode行为模式以及通用输出要求。

When to Use

适用场景

Running or chairing a cross-functional working session, project kickoff, stakeholder review, or decision meeting
Any meeting with more than three attendees or more than thirty minutes
Recurring meeting where a rolling structure (1-on-1, team sync) needs fresh framing each time
Mid-initiative alignment moment where explicit desired outcomes prevent drift

主持跨职能工作会议、项目启动会、利益相关方评审会或决策会议时
参会人数超过3人或时长超过30分钟的会议
需要每次更新框架的周期性会议（如1-on-1、团队同步会）
项目中期需要明确预期成果以避免偏离方向的对齐会议

When NOT to Use

不适用场景

The user's preparation is private and tactical (positioning, stakeholder reads, asks). Use
```
/meeting-brief
```
instead.
The meeting has already happened. Use
```
/meeting-recap
```
for post-meeting summarization.
The user wants to communicate outcomes to non-attendees. Use
```
/stakeholder-update
```
after the meeting.

用户的准备内容为私人战术性材料（如定位、利益相关方分析、诉求）：请改用
```
/meeting-brief
```
会议已结束：请使用
```
/meeting-recap
```
进行会后总结
用户需向非参会者传达会议成果：请在会后使用
```
/stakeholder-update
```

Zero-friction execution

零摩擦执行流程

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

Read all provided inputs (topic, any referenced files, attendee list, constraints)
Run inference on missing values (meeting type from topic keywords, duration default, objective from topic phrasing, attendee roles from context)
Present a brief inference summary and accept one-word
```
go
```
or corrections
Produce the agenda

If invoked with

--go

, skip the inference summary and produce output directly using defaults (duration 30 min, meeting type

other

, and so on). If the user provides all values upfront, no checkpoint appears.

Blocking questions are used only when inference confidence is actively low on a load-bearing input and no reasonable default exists. This should be rare.

根据家族协议，本Skill不会因询问而阻塞流程，默认执行流程如下：

读取所有提供的输入内容（议题、引用文件、参会者名单、约束条件）
对缺失值进行推断（通过议题关键词推断meeting type、默认时长、通过议题表述推断目标、通过上下文推断参会者角色）
展示简短的推断总结，接受单字指令
```
go
```
或修改意见
生成会议议程

如果通过

--go

指令调用，将跳过推断总结环节，直接使用默认值生成输出（默认时长30分钟、meeting type为

other

等）。若用户预先提供了所有必要值，则不会出现检查点。

仅当对关键输入的推断置信度极低且无合理默认值时，才会提出阻塞式问题，这种情况应极少发生。

Anti-meeting check

非会议必要性检查

This skill opens with an explicit question: "Does this need to be a meeting, or could it be handled async?"

v1.1.0: the check now requires a positive synchronous-value statement. The meeting passes the check only when at least one of these is named:

Tradeoff to discuss. multiple options, uncertain preference
Conflict to resolve. named stakeholders disagreeing
Co-creation. shared whiteboarding or document-writing in the meeting
Relationship-building. first-time stakeholder meeting, mutual calibration
Blocker escalation. time-sensitive unblocking

If none apply, the skill recommends the async alternative (written update, doc review, Slack poll) and produces a short one-page "how to handle this async" framing instead of an agenda.

The v1.0.0 version of this check ("single-owner decision with no tradeoffs", "pure information broadcast", "status-only sync with >5 people") was bypassed too easily. users would stay at five attendees or add "decision" to the topic. The stricter v1.1.0 biases toward async; users can still override.

This check is shared with

/meeting-brief

and not run by the post-meeting skills (recap, synthesize, stakeholder-update).

本Skill启动时会明确询问：“此事是否需要召开会议，还是可以通过异步方式处理？”

v1.1.0版本更新：检查现在要求明确说明同步沟通的价值。 仅当满足以下至少一项时，会议才通过检查：

需要讨论权衡方案：存在多个选项，偏好尚不明确
需要解决冲突：已明确的利益相关方存在分歧
需要协同创作：会议中需共同进行白板协作或文档撰写
需要建立关系：首次与利益相关方会面，需互相校准认知
需要升级解决阻塞问题：需及时解决阻碍进展的问题

若以上均不满足，本Skill会建议采用异步替代方案（如书面更新、文档评审、Slack投票），并生成一份简短的单页“异步处理指南”，而非会议议程。

v1.0.0版本的检查规则（“无权衡的单人决策”、“纯信息播报”、“仅同步状态且参会人数>5人”）过于容易被规避，用户只需将参会人数控制在5人以内或在议题中加入“决策”字样即可绕过。v1.1.0版本的规则更为严格，倾向于异步处理，但用户仍可选择覆盖该建议。

该检查规则与

/meeting-brief

共享，会后Skills（如recap、synthesize、stakeholder-update）不会执行此检查。

Instructions

操作步骤

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

Run anti-meeting check Apply the trigger patterns above. If the user's objective matches, propose the async alternative and ask for override. Only proceed to step 2 on explicit override.
Parse and load inputs Read the topic or purpose. Load all
```
@file
```
references provided. Extract any attendee list, time constraints, or linked documents.

Infer missing values Apply these inference rules:

Value	Inferred from	Default
Meeting type	Topic keywords, attendee seniority mix	`other` (low confidence)
Duration	Explicit in topic doc (rare); meeting-type-specific default when type is inferred at medium+ confidence	v1.1.0: type-specific (see family contract). 30 min only for `other` , `1-on-1` , `exec-briefing` , `customer-call` . Kickoff = 60, working-session = 60, decision-making = 45, etc.
Objective	Topic phrasing	Infer; surface in summary
Attendee RACI	Seniority, topic ownership cues	Flag all inferences
Desired outcomes	Objective plus meeting type heuristics	Offer strawman

Load-bearing inference gates (v1.1.0): when attendee RACI or desired outcomes are inferred below-high confidence, flag in the go-mode summary with

⚠

. See family contract "Zero-friction execution" section.

Present go-mode inference summary Show the inferred values with confidence markers. Accept
```
go
```
to proceed, or corrections to revise. Re-run inference after any correction and present the summary again.
Design the time-boxed topic list Apply the meeting-type variant (see below). Size topic times so their sum equals the meeting duration. If the topic list overflows the available time, flag it explicitly and ask for reconciliation (do not silently trim).

Each topic must have:
- Type tag:
```
Discussion | Decision | Information | Working
```
- Owner (name or team)
- Goal (what done looks like)
- Time allocation
- Pre-read link if any
Specify attendee prep List required prep with links and estimated prep time. Add recommended context for attendees who want deeper background. Add "come ready to" expectations that force clarity on what each attendee contributes.
Add parking lot and logistics placeholders Parking lot is a placeholder for off-topic items raised during the meeting. Logistics covers join link, materials needed, recording ownership.
Render the TEMPLATE.md with filled values Remove all guidance blockquotes from the final artifact.
Validate output
- Frontmatter shape conforms to the family contract's universal base fields plus agenda-specific fields (
```
meeting_duration_minutes
```
  ,
```
desired_outcomes
```
  )
- Sum of topic times equals meeting duration (+/- 2 min tolerance)
- At least one desired outcome is listed
- Anti-meeting check result is recorded in
```
Generation context
```

当被要求生成会议议程时，请遵循以下步骤：

执行非会议必要性检查 应用上述触发规则。若用户的目标符合异步处理场景，则提出异步替代方案并询问是否覆盖建议。仅在用户明确要求覆盖时，才进入步骤2。
解析并加载输入内容 读取议题或会议目的，加载所有提供的
```
@file
```
引用内容，提取参会者名单、时间约束或关联文档。

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

字段	推断依据	默认值
Meeting type	议题关键词、参会者层级构成	`other` （低置信度）
时长	议题文档中明确说明（少见）；当Meeting type推断置信度达到中等及以上时，使用对应类型的默认时长	v1.1.0：按类型区分（详见家族协议）。仅 `other` 、 `1-on-1` 、 `exec-briefing` 、 `customer-call` 默认30分钟。项目启动会=60分钟，工作会议=60分钟，决策会议=45分钟等
会议目标	议题表述	自动推断并在总结中展示
参会者RACI角色	层级、议题负责人线索	标记所有推断结果
预期成果	会议目标结合Meeting type启发规则	提供初步方案

关键推断校验（v1.1.0）：当参会者RACI角色或预期成果的推断置信度未达到高置信度时，需在go-mode总结中用

⚠

标记。详见家族协议的“零摩擦执行流程”章节。

展示go-mode推断总结 展示带有置信度标记的推断值，接受
```
go
```
指令继续或修改意见。若有修改，需重新执行推断并再次展示总结。
设计限时议题列表 应用对应的meeting type变体（见下文）。分配各议题时长，确保总时长等于会议时长。若议题列表总时长超出可用时间，需明确标记并请求协调（不得擅自删减）。

每个议题必须包含：
- 类型标签：
```
Discussion | Decision | Information | Working
```
- 负责人（姓名或团队）
- 目标（达成标准）
- 时间分配
- 预读链接（如有）
明确参会准备事项 列出所需准备内容及链接、预估准备时间。为需要深入了解背景的参会者添加推荐参考内容。加入“请准备好”的预期要求，明确每位参会者的贡献方向。
添加待议事项区和后勤信息占位符 待议事项区用于存放会议中提出的偏离主题的内容。后勤信息包含会议链接、所需材料、录屏负责人。
填充TEMPLATE.md模板并生成内容 最终成品中需移除所有指导性引用块。
验证输出内容
- 前置内容格式符合家族协议的通用基础字段及议程专属字段（
```
meeting_duration_minutes
```
  、
```
desired_outcomes
```
  ）
- 议题时长总和等于会议时长（允许±2分钟误差）
- 至少列出一项预期成果
- 非会议必要性检查结果已记录在
```
Generation context
```
  中

Meeting-type variants

Meeting type变体

Applied in step 5. Each variant reshapes the topic list to match the meeting's purpose.

1-on-1: Rolling structure. Last time's items, this time's topics, growth or development, blockers. Default 30 min.
standup: Status round-robin, escalations, decisions needed. Default 15 min.
planning: Commitments focus, capacity check, dependencies. Default 60 min.
review: Presentation-first, heavy pre-read, explicit feedback-capture mechanism. Default 60 min.
decision-making: Options upfront, decision criteria, explicit decision ask. Pre-read with proposal required. Default 45 min.
brainstorm: Minimal agenda, generative prompts, no decision pressure. Default 45 min.
stakeholder-review: TL;DR first, business-impact framing, explicit asks upfront. Default 45 min.
project-kickoff: Scope, roles, success criteria, risks, communication plan. Default 60 min.
working-session: Minimal agenda, pre-work required, explicit deliverable. Default 60 to 90 min.
exec-briefing: TL;DR first, supporting detail after. Default 30 min.
other: Generic topic structure, default 30 min.

在步骤5中应用，每个变体都会调整议题列表以匹配会议目的。

1-on-1：滚动式结构。包含上次遗留事项、本次议题、成长发展讨论、阻塞问题。默认时长30分钟。
standup：轮流汇报状态、升级问题、决策需求。默认时长15分钟。
planning：聚焦承诺事项、产能检查、依赖关系确认。默认时长60分钟。
review：先做演示、需提前阅读大量材料、明确反馈收集机制。默认时长60分钟。
decision-making：先列出选项、明确决策标准、提出明确决策请求。需提前阅读提案。默认时长45分钟。
brainstorm：极简议程、生成式引导、无决策压力。默认时长45分钟。
stakeholder-review：先展示核心要点（TL;DR）、从业务影响角度阐述、提前明确诉求。默认时长45分钟。
project-kickoff：讨论范围、角色、成功标准、风险、沟通计划。默认时长60分钟。
working-session：极简议程、需提前完成准备工作、明确交付成果。默认时长60-90分钟。
exec-briefing：先展示核心要点（TL;DR）、再补充支持细节。默认时长30分钟。
other：通用议题结构。默认时长30分钟。

Quality checklist

质量检查清单

Before delivering the agenda, verify:

Anti-meeting check was applied and recorded
Meeting type is set (or explicitly
```
other
```
with low-confidence flag)
Duration is set (default 30 min if not provided, flagged as default)
Desired outcomes are concrete and verifiable (not "discuss X" but "decide whether to ship X")
Every topic has type tag, owner, goal, time
Topic times sum to meeting duration
Pre-read prep time is listed (attendees skip prep when duration is not stated)
Logistics section has join link and materials references
Shareable summary is 5-6 lines, Slack-paste-ready
Sources and References section includes Generation context with defaults applied and inferences made

交付议程前，请验证以下内容：

已执行并记录非会议必要性检查
已设置Meeting type（或明确标记为
```
other
```
并标注低置信度）
已设置时长（未提供时默认30分钟，需标记为默认值）
预期成果具体可验证（例如“决定是否发布X”而非“讨论X”）
每个议题均包含类型标签、负责人、目标、时长
议题时长总和等于会议时长
已列出预读准备时间（若未说明时长，参会者可能会跳过准备）
后勤信息区包含会议链接和材料引用
可分享摘要为5-6行，适合直接粘贴到Slack
来源与参考部分包含
```
Generation context
```
，记录了应用的默认值和推断内容