meeting-synthesizer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Meeting Synthesizer Skill

会议整理器Skill

Transform raw meeting notes and transcripts into actionable intelligence. This skill extracts critical information from unstructured meeting data and organizes it into structured formats that drive follow-through and accountability.

将原始会议记录和转录文本转化为可落地的情报。该技能从非结构化的会议数据中提取关键信息，并将其整理为结构化格式，推动后续跟进与责任落实。

Overview

概述

The Meeting Synthesizer processes meeting notes or transcripts to produce:

Action Items: Clear tasks with owners, due dates, and context
Decisions Made: Key decisions with justification and implications
Discussion Points: Important topics, debates, and consensus areas
Follow-up Tasks: Prioritized task list with next steps
Key Insights: Patterns, concerns, and emerging themes

会议整理器处理会议记录或转录文本，生成以下内容：

行动项：明确的任务，包含负责人、截止日期和背景信息
已做出的决策：带有理由和影响的关键决策
讨论要点：重要议题、辩论和达成共识的领域
后续任务：带优先级的任务列表及下一步行动
关键洞察：模式、关注点和新兴主题

When to Use This Skill

使用场景

After team meetings, standups, or planning sessions
When converting transcript/notes into structured action items
When you need to quickly extract decisions and assign accountability
When synthesizing notes for stakeholders who missed the meeting
When creating task lists from meeting discussions

团队会议、站会或规划会议结束后
需要将转录文本/记录转化为结构化行动项时
需快速提取决策并明确责任归属时
为未参会的利益相关者整理会议记录时
从会议讨论中创建任务列表时

How to Use This Skill

使用方法

Basic Workflow

基础流程

Provide the Meeting Content
- Share meeting notes (typed or pasted)
- Share a transcript (from Zoom, Teams, or other platform)
- Share a voice-to-text transcription
Request Processing
- Ask the skill to synthesize the meeting
- Optionally specify which elements to focus on
- Optionally provide format preferences (markdown, JSON, etc.)
Review & Act
- Review the extracted information
- Assign owners and deadlines
- Create tickets or calendar items
- Share results with team

提供会议内容
- 分享会议记录（打字输入或粘贴）
- 分享转录文本（来自Zoom、Teams或其他平台）
- 分享语音转文字的转录内容
请求处理
- 要求该技能整理会议内容
- 可选择性指定需重点关注的内容模块
- 可选择性提供格式偏好（markdown、JSON等）
审阅并执行
- 审阅提取出的信息
- 分配负责人和截止日期
- 创建工单或日历事项
- 与团队分享结果

Example Prompts

示例提示词

Comprehensive Synthesis

全面整理

Synthesize this meeting:
[paste meeting notes/transcript]

Extract all action items, decisions, and key points.
Organize by priority and due date.

整理本次会议：
[粘贴会议记录/转录文本]

提取所有行动项、决策和关键要点。
按优先级和截止日期整理。

Focused on Action Items

聚焦行动项

Extract action items from this meeting:
[paste meeting notes]

For each action item, provide:
- Task description
- Owner/responsible person
- Due date (if mentioned)
- Context/why it matters
- Dependencies

从本次会议中提取行动项：
[粘贴会议记录]

每个行动项需包含：
- 任务描述
- 负责人
- 截止日期（如有提及）
- 背景/重要性
- 依赖项

Decision Extraction

决策提取

What decisions were made in this meeting?
[paste meeting notes]

For each decision, provide:
- What was decided
- Why (reasoning/justification)
- Who made the decision
- Who is affected
- Any dissent or concerns

本次会议做出了哪些决策？
[粘贴会议记录]

每个决策需包含：
- 决策内容
- 原因（推理/理由）
- 决策者
- 受影响方
- 异议或关注点

Priority Ordering

优先级排序

Synthesize this meeting with priority ordering:
[paste meeting notes]

Order action items by urgency and impact.
Identify any blocking items or critical path items.
Flag any decisions that need follow-up or clarification.

按优先级整理本次会议：
[粘贴会议记录]

按紧急程度和影响排序行动项。
识别阻塞项或关键路径项。
标记需要跟进或澄清的决策。

Processing Instructions

处理说明

1. Parse Meeting Content

1. 解析会议内容

Input Recognition:

Detect format: structured notes, transcript, bullet points, freeform text
Identify participants: who attended, who spoke, roles
Extract timestamps: when discussed (if available)
Recognize context: meeting type, agenda, goals

Normalization:

Clean up formatting inconsistencies
Expand abbreviations where possible
Clarify ambiguous references
Group related items

输入识别：

检测格式：结构化记录、转录文本、项目符号、自由格式文本
识别参与者：参会人员、发言者、角色
提取时间戳：讨论时间（如有提供）
识别背景：会议类型、议程、目标

标准化处理：

清理格式不一致的内容
尽可能展开缩写
明确模糊的指代
分组相关内容

2. Extract Action Items

2. 提取行动项

Identification:

Look for explicit assignments: "Alice will...", "We need to..."
Identify implicit tasks: decisions requiring implementation
Find time-bound items: "by Friday", "next sprint", "ASAP"
Recognize dependencies: "after X is done"

Structuring:

Action Item:
  Description: [Clear, specific task]
  Owner: [Person responsible]
  Due: [Date/timeline]
  Context: [Why it matters]
  Dependencies: [What must happen first]
  Priority: [High/Medium/Low]

识别：

寻找明确的任务分配：“Alice将...”, “我们需要...”
识别隐含任务：需要落地的决策
找到有时间限制的事项：“周五前”, “下个迭代”, “尽快”
识别依赖项：“在X完成后”

结构化：

行动项：
  描述：[清晰、具体的任务]
  负责人：[责任人]
  截止日期：[日期/时间线]
  背景：[重要性]
  依赖项：[需先完成的事项]
  优先级：[高/中/低]

3. Identify Decisions

3. 识别决策

Detection:

Explicit decisions: "We decided to...", "We will..."
Consensus moments: "Everyone agreed...", "Consensus is..."
Choices made: "We chose X over Y"
Direction changes: "We're shifting from X to Y"

Documentation:

Decision:
  What: [The decision]
  Why: [Reasoning/justification]
  Decided By: [Who decided]
  Affected: [Who is impacted]
  Dissent: [Any concerns/opposition]
  Implementation: [How will it work]

检测：

明确的决策：“我们决定...”, “我们将...”
共识时刻：“所有人同意...”, “共识是...”
做出的选择：“我们选择X而非Y”
方向变更：“我们从X转向Y”

记录：

决策：
  内容：[决策事项]
  原因：[推理/理由]
  决策者：[做出决策的人/群体]
  受影响方：[受影响的人/群体]
  异议：[任何顾虑/反对意见]
  落地方式：[执行方案]

4. Capture Discussion Points

4. 记录讨论要点

Extraction:

Main topics discussed
Debates or different viewpoints
Open questions or uncertainties
Agreed-upon principles or approaches

Organization:

Discussion Point:
  Topic: [What was discussed]
  Viewpoints: [Different perspectives]
  Consensus: [What was agreed]
  Open Issues: [Unresolved items]

提取：

讨论的主要议题
辩论或不同观点
未解决的问题或不确定性
达成共识的原则或方法

组织：

讨论要点：
  议题：[讨论内容]
  观点：[不同视角]
  共识：[达成的一致意见]
  未解决事项：[待解决的问题]

5. Generate Follow-up Tasks

5. 生成后续任务

Identification:

Clarification needed: "We should confirm with X"
Information gathering: "Research options for Y"
Scheduling: "Schedule sync with Z"
Communication: "Update stakeholders on decision"

Prioritization:

Critical: Blocks other work, high impact
High: Important, needed soon
Medium: Should be done, no immediate urgency
Low: Nice to have, lower priority

识别：

需要澄清的内容：“我们应与X确认”
信息收集：“研究Y的选项”
日程安排：“安排与Z的同步会议”
沟通：“向利益相关者更新决策”

优先级划分：

关键：阻塞其他工作，影响重大
高：重要，需尽快完成
中：应尽快完成，无紧急需求
低：锦上添花，优先级较低

Output Format

输出格式

Option 1: Markdown (Default)

选项1：Markdown（默认）

markdown

undefined

markdown

undefined

Meeting Synthesis: [Meeting Title/Date]

会议整理：[会议标题/日期]

Participants

参与者

Alice (Product Lead)
Bob (Engineering)
Carol (Design)

Alice（产品负责人）
Bob（工程师）
Carol（设计师）

Decisions Made

已做出的决策

Decision 1

决策1

What: Adopt Vue 3 for new frontend
Why: Better TypeScript support, smaller bundle size
Decided: By consensus
Impact: Requires training for team members using Vue 2

内容：采用Vue 3开发新前端
原因：更好的TypeScript支持，更小的包体积
决策者：共识
影响：需要为使用Vue 2的团队成员提供培训

Decision 2

决策2

What: Delay launch by 2 weeks
Why: Need more time for security review
Decided: Product + Security alignment
Impact: Affects Q4 roadmap planning

内容：将发布推迟2周
原因：需要更多时间进行安全审查
决策者：产品+安全部门对齐
影响：影响Q4路线图规划

Action Items

行动项

High Priority

高优先级

Complete security audit (Bob, Due: Friday)
Prepare Vue 3 migration plan (Carol, Due: Monday)

完成安全审计（Bob，截止：周五）
准备Vue 3迁移计划（Carol，截止：周一）

Medium Priority

中优先级

Schedule team Vue 3 training (Alice, Due: Next week)

安排团队Vue 3培训（Alice，截止：下周）

Low Priority

低优先级

Document decision rationale (Bob, Due: End of sprint)

记录决策理由（Bob，截止：迭代结束）

Key Discussion Points

关键讨论要点

Concerns about timeline slippage
Team enthusiasm for Vue 3 adoption
Need for better documentation

对时间线延迟的担忧
团队对Vue 3采用的热情
对更完善文档的需求

Follow-up Required

需跟进事项

Confirm security audit scope with CTO
Get client approval for 2-week delay
Check team training capacity

undefined

与CTO确认安全审计范围
获得客户对2周延迟的批准
检查团队培训能力

undefined

Option 2: JSON Structure

选项2：JSON结构

json

{
  "meeting": {
    "title": "Q4 Planning",
    "date": "2024-11-08",
    "participants": ["Alice", "Bob", "Carol"]
  },
  "decisions": [
    {
      "id": "D1",
      "description": "Adopt Vue 3",
      "rationale": "Better TS support",
      "decider": "Consensus",
      "impact": "Requires team training"
    }
  ],
  "actionItems": [
    {
      "id": "A1",
      "task": "Complete security audit",
      "owner": "Bob",
      "dueDate": "2024-11-10",
      "priority": "HIGH",
      "context": "Required before launch"
    }
  ],
  "followUp": ["Confirm security audit scope", "Get client approval"]
}

json

{
  "meeting": {
    "title": "Q4规划",
    "date": "2024-11-08",
    "participants": ["Alice", "Bob", "Carol"]
  },
  "decisions": [
    {
      "id": "D1",
      "description": "采用Vue 3",
      "rationale": "更好的TS支持",
      "decider": "Consensus",
      "impact": "需要团队培训"
    }
  ],
  "actionItems": [
    {
      "id": "A1",
      "task": "完成安全审计",
      "owner": "Bob",
      "dueDate": "2024-11-10",
      "priority": "HIGH",
      "context": "发布前必需"
    }
  ],
  "followUp": ["确认安全审计范围", "获得客户批准"]
}

Examples

示例

Example 1: Product Planning Meeting

示例1：产品规划会议

Input Meeting Notes:

Meeting: Product Planning - Q1 2025
Attendees: Sarah (PM), Mike (Lead Dev), Lisa (Designer)

Topics:
1. User feedback analysis - lots of requests for dark mode
2. Performance issues reported in production
3. Q1 roadmap planning

Decisions:
- Will implement dark mode as primary feature
- Will address performance issues first (performance is blocking)
- Delaying mobile app until Q2

Action items:
Sarah will brief the team on user feedback by tomorrow
Mike will create performance improvement plan by Friday
Lisa will start dark mode design exploration next week
Need to schedule meeting with exec team for roadmap approval

Issues:
- Performance work might delay features
- Team capacity might be tight with both performance + dark mode
- Mobile app delay will disappoint some users

Output:

markdown

undefined

输入会议记录：

会议：2025年Q1产品规划
参会者：Sarah（产品经理）、Mike（首席开发）、Lisa（设计师）

议题：
1. 用户反馈分析 - 大量用户请求深色模式
2. 生产环境中报告的性能问题
3. Q1路线图规划

决策：
- 将深色模式作为核心功能开发
- 优先解决性能问题（性能是阻塞项）
- 将移动应用推迟到Q2

行动项：
Sarah需在明天前向团队介绍用户反馈
Mike需在周五前制定性能改进计划
Lisa需在下周开始深色模式设计探索
需安排与高管团队的路线图审批会议

问题：
- 性能工作可能会延迟功能开发
- 同时处理性能和深色模式可能导致团队产能紧张
- 移动应用推迟会让部分用户失望

输出：

markdown

undefined

Q1 2025 Product Planning Synthesis

2025年Q1产品规划整理

Decisions

决策

Implement dark mode as primary Q1 feature
- Why: High user demand from feedback analysis
- Impact: Becomes focus of design/feature work
Prioritize performance issues before new features
- Why: Blocking production users
- Impact: Requires dedicated engineering time first
Delay mobile app to Q2
- Why: Capacity and roadmap constraints
- Impact: Will disappoint some users, needs communication

将深色模式作为Q1核心功能开发
- 原因：用户反馈中需求强烈
- 影响：成为设计/功能工作的重点
在新功能开发前优先解决性能问题
- 原因：阻塞生产环境用户使用
- 影响：需要投入专门的工程师时间
将移动应用推迟到Q2
- 原因：产能和路线图限制
- 影响：会让部分用户失望，需要沟通

Action Items

行动项

Critical Path

关键路径

Performance improvement plan (Mike, Due: Friday)
- Context: Blocking roadmap
- Unblocks: Dark mode feature work

性能改进计划（Mike，截止：周五）
- 背景：阻塞路线图
- 解锁：深色模式功能开发

High Priority

高优先级

Team briefing on user feedback (Sarah, Due: Tomorrow)
Dark mode design exploration (Lisa, Due: Next week)

向团队介绍用户反馈（Sarah，截止：明天）
深色模式设计探索（Lisa，截止：下周）

Follow-up Required

需跟进事项

Executive team meeting on Q1 roadmap
Communication plan for mobile app delay
Capacity planning for parallel work streams

与高管团队的Q1路线图会议
移动应用推迟的沟通计划
并行工作流的产能规划

Key Concerns

关键关注点

Tight team capacity with performance + dark mode
Mobile app delay needs stakeholder management
Performance work timeline might slip

undefined

同时处理性能和深色模式导致团队产能紧张
移动应用推迟需要利益相关者管理
性能工作时间线可能延迟

undefined

Example 2: Engineering Standup

示例2：工程站会

Input Transcript:

Sarah: OK team, quick standup. Mike, how's the API work?

Mike: Good progress. Got the authentication endpoints done.
Got the rate limiting working. Should be done by EOW.

Sarah: Great. Any blockers?

Mike: Need DB schema review from Carol. That's blocking
the user service implementation.

Carol: Oh, I can look at that this afternoon. Will send feedback.

Sarah: Perfect. Lisa, how's the frontend?

Lisa: Integrated the new modal component. Ran into a
responsive design issue on mobile that I'm debugging.
Should have fixed by tomorrow.

Sarah: OK, don't spend too much time on that if it's complex.
We can handle edge cases later.

Mike: Also, we should probably do a load test before shipping.

Sarah: Agreed. Let's add that to the list. Carol, can you
help set that up?

Carol: Sure, I can coordinate with DevOps.

Sarah: Good. Let's reconvene Thursday to check in.

Output:

markdown

undefined

输入转录文本：

Sarah：好的团队，快速站会。Mike，API工作进展如何？

Mike：进展顺利。认证端点已完成。
限流功能已实现。预计本周末完成。

Sarah：很好。有阻塞项吗？

Mike：需要Carol审核数据库 schema。这阻塞了用户服务的开发。

Carol：哦，我今天下午可以看。会发送反馈。

Sarah：完美。Lisa，前端进展如何？

Lisa：已集成新的模态框组件。遇到了移动端响应式设计问题，正在调试。
预计明天前修复。

Sarah：好的，如果问题复杂就不要花太多时间。
我们之后再处理边缘情况。

Mike：另外，我们可能需要在发布前做负载测试。

Sarah：同意。把这个加到列表里。Carol，你能
帮忙安排吗？

Carol：没问题，我可以和DevOps协调。

Sarah：好的。我们周四再开会检查进展。

输出：

markdown

undefined

Engineering Standup - 2024-11-08

工程站会 - 2024-11-08

Current Status

当前状态

Mike: API auth endpoints complete, rate limiting working
- On track: EOW completion
- Blocker: Waiting on DB schema review
Lisa: Modal component integrated, debugging responsive issue
- On track: Mobile fix by tomorrow
- Note: Don't over-engineer edge cases
Carol: Available for schema review, coordinating load testing

Mike：API认证端点已完成，限流功能已实现
- 进度：本周末完成
- 阻塞项：等待数据库schema审核
Lisa：已集成模态框组件，正在调试移动端响应式问题
- 进度：明天前修复
- 备注：不要过度设计边缘情况
Carol：可进行schema审核，协调负载测试

Action Items

行动项

High Priority

高优先级

DB schema review (Carol, Due: Today afternoon)
- Unblocks: Mike's user service implementation
Mobile responsive debugging (Lisa, Due: Tomorrow)
- Context: Modal component issue

数据库schema审核（Carol，截止：今天下午）
- 解锁：Mike的用户服务开发
移动端响应式问题调试（Lisa，截止：明天）
- 背景：模态框组件问题

Medium Priority

中优先级

Coordinate load testing setup (Carol + DevOps, Due: This week)
- Context: Required before shipping

协调负载测试设置（Carol + DevOps，截止：本周）
- 背景：发布前必需

Decisions

决策

Load testing is required before deployment
Don't over-engineer mobile edge cases yet

发布前需进行负载测试
暂不过度设计移动端边缘情况

Next Check-in

下次检查

Thursday team standup for progress review

undefined

周四团队站会检查进展

undefined

Processing Tips

处理技巧

Handle Ambiguity

处理模糊内容

If owner unclear: Note "TBD" and flag for clarification
If timeline unclear: Use phrases like "asap", "this week", "unclear timeline"
If decision unclear: List as "discussion item" vs "decision"

若负责人不明确：标记为“待确定”并提醒需澄清
若时间线不明确：使用“尽快”、“本周”、“时间线不明”等表述
若决策不明确：列为“讨论项”而非“决策”

Identify Hidden Items

识别隐藏事项

"We should..." often means someone needs to do it
"Someone will need to..." is an implicit action item
"We need to verify..." is a follow-up task
"Can you..." is an action item for the person being asked

“我们应该...”通常意味着需要有人去执行
“需要有人去...”是隐含的行动项
“我们需要验证...”是后续任务
“你能...”是对被询问者的行动项

Prioritize Effectively

有效优先级划分

Critical: Blocks other work
High: Time-sensitive or important
Medium: Should be done soon
Low: Nice to have

关键：阻塞其他工作
高：时间敏感或重要
中：应尽快完成
低：锦上添花

Red Flags

危险信号

Vague ownership ("we'll figure it out")
No timeline mentioned
Conflicting decisions
Unresolved concerns
Unclear next steps

模糊的责任归属（“我们之后再想”）
未提及时间线
冲突的决策
未解决的关注点
不明确的下一步行动

Best Practices

最佳实践

Input Quality

输入质量

More detail is better (full transcript > vague summary)
Include speaker names if available
Preserve disagreements and concerns
Note time-sensitive items

细节越多越好（完整转录文本 > 模糊摘要）
如有提供，包含发言者姓名
保留不同意见和关注点
标记时间敏感事项

Output Quality

输出质量

Be specific: "review code" not clear, "review API endpoint authentication code" is clear
Include context: Why matters, not just what to do
Flag dependencies: What must happen first
Highlight urgency: Critical path items

具体：“审核代码”不够清晰，“审核API端点认证代码”更明确
包含背景：不仅要说明做什么，还要说明为什么重要
标记依赖项：需先完成的事项
突出紧急性：关键路径项

Follow-Through

跟进执行

Share results with team members assigned
Create tickets/calendar items for action items
Schedule follow-up for open items
Update stakeholders on decisions

与被分配任务的团队成员分享结果
为行动项创建工单/日历事项
为未解决事项安排跟进
向利益相关者更新决策

Common Patterns

常见模式

Pattern 1: Decision with Cascading Action Items

模式1：决策引发的连锁行动项

Decision: Use PostgreSQL instead of MongoDB
  ↓
Action Items:
- Migrate existing data (Owner: DB team)
- Update ORM code (Owner: Backend team)
- Update schema documentation (Owner: Docs)
- Train team on SQL (Owner: Tech lead)

决策：使用PostgreSQL而非MongoDB
  ↓
行动项：
- 迁移现有数据（负责人：数据库团队）
- 更新ORM代码（负责人：后端团队）
- 更新schema文档（负责人：文档团队）
- 培训团队使用SQL（负责人：技术主管）

Pattern 2: Blocking Dependencies

模式2：阻塞依赖

Task A: Complete security audit (BLOCKING)
  ↓
Task B: Deploy to production (BLOCKED)
  ↓
Task C: Start Q2 roadmap planning (BLOCKED)

任务A：完成安全审计（阻塞项）
  ↓
任务B：部署到生产环境（被阻塞）
  ↓
任务C：开始Q2路线图规划（被阻塞）

Pattern 3: Decision Reversal or Clarification Needed

模式3：决策反转或需澄清

Stated: "We'll use Vue"
But earlier: "React is better"
Follow-up: Clarify decision rationale and communicate to team

表述：“我们将使用Vue”
但之前：“React更好”
跟进：澄清决策理由并与团队沟通

Quality Checklist

质量检查清单

Integration Points

集成点

With Task Management

与任务管理工具集成

Export action items to Jira, GitHub Issues, Asana
Create calendar items for deadlines
Set up reminders for owners

将行动项导出到Jira、GitHub Issues、Asana
为截止日期创建日历事项
为负责人设置提醒

With Communication

与沟通工具集成

Share synthesis with team
Send to stakeholders who couldn't attend
Create meeting summary email

与团队分享整理结果
发送给未参会的利益相关者
创建会议总结邮件

With Roadmap Planning

与路线图规划集成

Decisions impact roadmap/timeline
Action items affect capacity planning
Follow-up tasks might become next meeting agenda

决策影响路线图/时间线
行动项影响产能规划
后续任务可能成为下次会议的议程

Limitations & Considerations

局限性与注意事项

Cannot identify non-verbal communication (tone, body language)
May miss implicit context only meeting attendees understand
Requires clear, interpretable notes or transcripts
Ambiguous meeting notes produce ambiguous output
Cannot follow up on decisions that weren't explicit

无法识别非语言沟通（语气、肢体语言）
可能会遗漏只有参会者才理解的隐含背景
需要清晰、可解释的记录或转录文本
模糊的会议记录会产生模糊的输出
无法跟进未明确表述的决策