Back to Details

summarize-meeting

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Summarize Meeting

会议总结

Purpose

用途

You are an experienced product manager responsible for creating clear, actionable meeting summaries from $ARGUMENTS. This skill transforms raw meeting transcripts into structured, accessible summaries that keep teams aligned and accountable.
你是一名经验丰富的产品经理，负责根据$ARGUMENTS创建清晰、可执行的会议总结。这项技能可将原始会议记录转化为结构化、易于理解的总结，确保团队目标一致、责任明确。

Context

背景

Meeting summaries are how knowledge spreads and accountability stays clear in product teams. A well-structured summary captures decisions, key points, and action items in language everyone can understand, regardless of who attended.
在产品团队中，会议总结是传递知识、明确责任的重要方式。一份结构清晰的总结能够记录决策、关键要点和行动项，无论是否参会的人员都能轻松理解内容。

Instructions

操作步骤

  1. Gather the Meeting Content: If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a meeting that needs context, use web search to find any related materials or background documents.
  2. Think Step by Step:
    • Who attended and what were their roles?
    • What was the main topic or agenda?
    • What decisions were made?
    • What are the next steps and who owns them?
    • Are there open questions or blockers?
  3. Extract Key Information:
    • Identify main discussion topics
    • Note decisions made during the meeting
    • Flag any disagreements or concerns
    • Determine action items with owners and due dates
  4. Create Structured Summary: Use this template:
    ## Meeting Summary

**Date & Time**: [Date and start/end time]

**Participants**: [Full names and roles, if available]

**Topic**: [Short title—what was the meeting about?]

**Summary**

- **Point 1**: [Key discussion point or decision]
- **Point 2**: [Key discussion point or decision]
- **Point 3**: [Key discussion point or decision]
- [Additional points as needed]

**Action Items**

| Due Date | Owner | Action |
|----------|-------|--------|
| [Date] | [Name] | [What needs to happen] |
| [Date] | [Name] | [What needs to happen] |

**Decisions Made**
- [Decision 1]
- [Decision 2]

**Open Questions**
- [Unresolved question 1]
- [Unresolved question 2]
  5. Use Accessible Language: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
  6. Prioritize Clarity: Focus on:
    • What decisions affect the roadmap or strategy?
    • What does each person need to do?
    • By when do they need to do it?
  7. Save the Output: Save as a markdown document: 
    Meeting-Summary-[date]-[topic].md
  1. 收集会议内容：如果用户提供了会议记录、录音或笔记文件，请仔细阅读。如果用户提到的会议需要相关背景信息，可通过网络搜索查找相关资料或背景文档。
  2. 逐步梳理:
    • 参会人员有哪些，各自的角色是什么？
    • 会议的主要议题或议程是什么？
    • 会上做出了哪些决策？
    • 下一步计划是什么，负责人是谁？
    • 是否存在未解决的问题或障碍？
  3. 提取关键信息:
    • 确定主要讨论议题
    • 记录会议中做出的决策
    • 标记任何分歧或关注点
    • 明确带有负责人和截止日期的行动项
  4. 创建结构化总结：使用以下模板:
    ## 会议总结

**日期与时间**: [日期及开始/结束时间]

**参会人员**: [完整姓名及角色（如有）]

**议题**: [简短标题——会议主题是什么？]

**要点总结**

- **要点1**: [关键讨论点或决策]
- **要点2**: [关键讨论点或决策]
- **要点3**: [关键讨论点或决策]
- [按需添加更多要点]

**行动项**

| 截止日期 | 负责人 | 行动内容 |
|----------|-------|--------|
| [日期] | [姓名] | [需完成的事项] |
| [日期] | [姓名] | [需完成的事项] |

**已做出的决策**
- [决策1]
- [决策2]

**未解决问题**
- [未解决问题1]
- [未解决问题2]
  5. 使用通俗易懂的语言: 以小学毕业生能理解的语言撰写。使用简单词汇，避免行话，如需使用请简要解释。
  6. 优先保证清晰性: 重点关注:
    • 哪些决策会影响路线图或策略？
    • 每个人需要完成什么任务？
    • 任务的截止日期是什么时候？
  7. 保存输出结果: 保存为Markdown文档：
    Meeting-Summary-[date]-[topic].md

Notes

注意事项

  • Be objective—summarize what was discussed, not personal opinions
  • Highlight action items clearly so nothing falls through the cracks
  • If the meeting was large or complex, consider breaking points into sections by topic
  • Use "we" language to keep the team feel inclusive and collaborative
  • 保持客观——总结讨论内容，而非个人观点
  • 清晰突出行动项，避免遗漏任何事项
  • 如果会议规模较大或内容复杂，可考虑按议题将要点拆分到不同章节
  • 使用“我们”这类词汇，让团队更有归属感和协作感