Back to Details

meeting-notes

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Meeting Notes

会议笔记处理工具

Overview

概述

This skill transforms raw meeting notes, transcripts, or audio summaries into clear, structured documentation with action items, decisions, and key takeaways.
Use Cases:
  • Converting messy handwritten notes to clean summaries
  • Processing meeting transcripts
  • Extracting action items and owners
  • Creating meeting minutes for distribution
  • Summarizing long discussions into key points
本Skill可将原始会议笔记、转录稿或音频摘要转换为结构清晰的文档，包含行动项、决策内容和关键要点。
适用场景：
  • 将杂乱的手写笔记转换为整洁的摘要
  • 处理会议转录稿
  • 提取行动项及负责人
  • 生成可分发的会议纪要
  • 将冗长讨论内容提炼为关键要点

How to Use

使用方法

  1. Paste your raw meeting notes, transcript, or description
  2. Tell me the meeting type (standup, project review, client call, etc.)
  3. Specify any required format or template
  4. I'll create structured notes with action items
Example prompts:
  • "Organize these meeting notes and extract action items"
  • "Create formal meeting minutes from this transcript"
  • "Summarize the key decisions from our project review"
  • "Turn this brainstorm session into a structured document"
  1. 粘贴你的原始会议笔记、转录稿或会议描述
  2. 告知我会议类型（站会、项目评审、客户沟通会等）
  3. 指定所需的格式或模板
  4. 我将生成包含行动项的结构化笔记
示例提示词：
  • "整理这些会议笔记并提取行动项"
  • "根据这份转录稿生成正式会议纪要"
  • "总结我们项目评审中的关键决策"
  • "将这次头脑风暴会议内容转换为结构化文档"

Meeting Note Templates

会议笔记模板

Standard Meeting Summary

标准会议摘要

markdown
undefined
markdown
undefined

Meeting Summary

会议摘要

Meeting: [Title] Date: [Date] Attendees: [Names] Duration: [Time]
会议主题： [标题] 日期： [日期] 参会人员： [姓名] 时长： [时间]

Purpose

会议目的

[One sentence describing meeting objective]
[一句话描述会议目标]

Key Discussion Points

关键讨论要点

  1. [Topic 1]
    • [Key point]
    • [Key point]
  2. [Topic 2]
    • [Key point]
    • [Key point]
  1. [议题1]
    • [关键点]
    • [关键点]
  2. [议题2]
    • [关键点]
    • [关键点]

Decisions Made

已做出的决策

  • [Decision 1]
  • [Decision 2]
  • [决策1]
  • [决策2]

Action Items

行动项

ActionOwnerDue DateStatus
[Task][Name][Date]Pending
行动内容负责人截止日期状态
[任务][姓名][日期]待处理

Next Steps

后续步骤

  • [Next meeting/milestone]
  • [下次会议/里程碑]

Notes

补充说明

[Any additional context or parking lot items]
undefined
[任何额外背景信息或暂不处理的事项]
undefined

Quick Standup Notes

快速站会笔记

markdown
undefined
markdown
undefined

Daily Standup - [Date]

每日站会 - [日期]

[Team Member 1]

[团队成员1]

Yesterday: [Completed tasks] Today: [Planned tasks] Blockers: [Issues, if any]
昨日完成： [已完成任务] 今日计划： [计划任务] 阻塞问题： [存在的问题（如有）]

[Team Member 2]

[团队成员2]

...
...

Team Blockers

团队阻塞问题

  • [Blocker requiring escalation]
  • [需要升级处理的阻塞项]

Announcements

通知事项

  • [Team-wide updates]
undefined
  • [团队范围的更新内容]
undefined

Client Meeting Notes

客户会议笔记

markdown
undefined
markdown
undefined

Client Meeting Notes

客户会议笔记

Client: [Company Name] Date: [Date] Our Team: [Names] Client Team: [Names]
客户公司： [公司名称] 日期： [日期] 我方团队： [姓名] 客户团队： [姓名]

Meeting Objective

会议目标

[Why we met]
[召开本次会议的原因]

Client Feedback/Requests

客户反馈/需求

  1. [Feedback point]
  2. [Request]
  1. [反馈要点]
  2. [需求内容]

Our Commitments

我方承诺

  • [What we promised to deliver]
  • [Timeline]
  • [我们承诺交付的内容]
  • [时间线]

Client Commitments

客户承诺

  • [What they will provide]
  • [Timeline]
  • [客户将提供的内容]
  • [时间线]

Follow-up Required

后续跟进事项

ItemOwnerDue
[Task][Name][Date]
事项负责人截止日期
[任务][姓名][日期]

Next Meeting

下次会议

[Date/Time/Agenda preview]
undefined
[日期/时间/议程预览]
undefined

Project Review Notes

项目评审笔记

markdown
undefined
markdown
undefined

Project Review: [Project Name]

项目评审：[项目名称]

Date: [Date] Phase: [Current phase] Status: 🟢 On Track / 🟡 At Risk / 🔴 Off Track
日期： [日期] 阶段： [当前阶段] 状态： 🟢 按计划推进 / 🟡 存在风险 / 🔴 偏离计划

Progress Update

进度更新

  • Completed: [Milestones achieved]
  • In Progress: [Current work]
  • Upcoming: [Next milestones]
  • 已完成： [达成的里程碑]
  • 进行中： [当前工作内容]
  • 待启动： [下一个里程碑]

Metrics

指标数据

MetricTargetActualStatus
[KPI][Target][Actual]✅/⚠️/❌
指标目标值实际值状态
[关键绩效指标][目标][实际]✅/⚠️/❌

Risks & Issues

风险与问题

Risk/IssueImpactMitigationOwner
[Description]High/Med/Low[Plan][Name]
风险/问题影响程度缓解方案负责人
[描述]高/中/低[计划][姓名]

Decisions Needed

待决策事项

  • [Decision requiring escalation]
  • [需要升级决策的事项]

Action Items

行动项

  • [Task] - @[Owner] - Due: [Date]
undefined
  • [任务] - @[负责人] - 截止日期：[日期]
undefined

Processing Guidelines

处理规则

Extracting Action Items

提取行动项

Look for phrases indicating tasks:
  • "We need to..." / "Someone should..."
  • "Can you..." / "Will you..."
  • "Let's..." / "Action:"
  • Names + verbs (e.g., "John will prepare...")
  • Deadlines mentioned with tasks
寻找表示任务的表述：
  • "我们需要..." / "有人应该..."
  • "你能否..." / "你会..."
  • "我们来..." / "行动："
  • 姓名+动词（例如："John将准备..."）
  • 与任务关联的截止日期

Identifying Decisions

识别决策内容

Look for:
  • "We've decided..." / "The decision is..."
  • "Going forward, we will..."
  • "Agreed:" / "Confirmed:"
  • Consensus language ("everyone agreed...")
寻找以下表述：
  • "我们已决定..." / "决策内容是..."
  • "今后，我们将..."
  • "已同意：" / "已确认："
  • 达成共识的表述（"所有人同意..."）

Determining Owners

确定负责人

  • Explicitly named: "Sarah will handle..."
  • Role-based: "The design team will..."
  • Default to meeting organizer if unclear
  • Flag unassigned items for follow-up
  • 明确指定的人员："Sarah将负责..."
  • 基于角色的："设计团队将..."
  • 若不明确则默认会议组织者
  • 标记未分配的事项以便跟进

Output Format

输出格式

markdown
undefined
markdown
undefined

Meeting Summary: [Title]

会议摘要：[标题]

📅 Date: [Date] 👥 Attendees: [List]
📅 日期： [日期] 👥 参会人员： [列表]

📋 Summary

📋 摘要

[2-3 sentence overview]
[2-3句话的概述]

💡 Key Points

💡 关键要点

  1. [Point 1]
  2. [Point 2]
  3. [Point 3]
  1. [要点1]
  2. [要点2]
  3. [要点3]

✅ Decisions

✅ 已做出的决策

  • [Decision 1]
  • [Decision 2]
  • [决策1]
  • [决策2]

📌 Action Items

📌 行动项

#ActionOwnerDuePriority
1[Task][Name][Date]High/Med/Low
序号行动内容负责人截止日期优先级
1[任务][姓名][日期]高/中/低

🔜 Next Steps

🔜 后续步骤

  • [Next meeting or milestone]
  • [下次会议或里程碑]

📝 Parking Lot

📝 暂存事项

  • [Items to address later]
undefined
  • [后续再处理的事项]
undefined

Customization Options

自定义选项

Tell me your preferences:
  • Format: Bullet points, table, prose, or formal minutes
  • Detail level: Executive summary, standard, or detailed
  • Focus: Action items only, decisions only, or comprehensive
  • Style: Casual team notes or formal documentation
告知你的偏好：
  • 格式： 项目符号、表格、散文式或正式纪要
  • 详细程度： 执行摘要、标准版本或详细版本
  • 重点： 仅行动项、仅决策内容或完整内容
  • 风格： 非正式团队笔记或正式文档

Limitations

局限性

  • Cannot attend or record meetings
  • Accuracy depends on quality of input notes
  • May need clarification on ambiguous pronouns or acronyms
  • Cannot verify commitments or deadlines - review before distributing
  • 无法参会或录制会议
  • 输出准确性依赖于输入笔记的质量
  • 可能需要对模糊的代词或缩写进行澄清
  • 无法核实承诺内容或截止日期——分发前请审核

Examples

示例

Example: Raw Notes to Structured Summary

示例：原始笔记转换为结构化摘要

Input:
product meeting 3/15
talked about launch timeline, sarah thinks we need 2 more weeks
john mentioned the bug in checkout - high priority
decided to push launch to april 1
need to update stakeholders
maria will fix the checkout bug by friday
also discussed new feature requests from customers - will prioritize next sprint
john to send customer feedback summary
Output:
输入：
产品会议 3/15
talked about launch timeline, sarah thinks we need 2 more weeks
john mentioned the bug in checkout - high priority
decided to push launch to april 1
need to update stakeholders
maria will fix the checkout bug by friday
also discussed new feature requests from customers - will prioritize next sprint
john to send customer feedback summary
输出：

Meeting Summary: Product Launch Review

会议摘要：产品发布评审

📅 Date: March 15, 2024 👥 Attendees: Sarah, John, Maria
📅 日期： 2024年3月15日 👥 参会人员： Sarah, John, Maria

📋 Summary

📋 摘要

Reviewed launch timeline and decided to postpone launch by 2 weeks to April 1 due to critical checkout bug. Discussed customer feature requests for future prioritization.
本次会议评审了产品发布时间线，由于发现结账流程中的关键bug，决定将发布时间推迟2周至4月1日。同时讨论了客户新功能需求，将在下一个迭代中优先处理。

💡 Key Points

💡 关键要点

  1. Original launch timeline insufficient - need 2 more weeks
  2. Critical checkout bug discovered - must fix before launch
  3. Customer feature requests collected for next sprint prioritization
  1. 原发布时间线不足，需要额外2周时间
  2. 发现结账流程中的关键bug，必须在发布前修复
  3. 已收集客户新功能需求，将在下一个迭代规划中优先考虑

✅ Decisions

✅ 已做出的决策

  • Launch date moved from mid-March to April 1
  • Checkout bug is highest priority
  • Feature requests to be prioritized in next sprint planning
  • 发布日期从3月中旬调整为4月1日
  • 结账bug为最高优先级
  • 客户新功能需求将在下次迭代规划中优先处理

📌 Action Items

📌 行动项

#ActionOwnerDuePriority
1Fix checkout bugMariaFriday (3/17)🔴 High
2Update stakeholders on new launch date[Unassigned]ASAP🔴 High
3Send customer feedback summaryJohn[TBD]🟡 Medium
序号行动内容负责人截止日期优先级
1修复结账bugMaria3月17日（周五）🔴 高
2向利益干系人更新新的发布日期[未分配]尽快🔴 高
3发送客户反馈摘要John[待确定]🟡 中

🔜 Next Steps

🔜 后续步骤

  • Follow-up on bug fix progress
  • Stakeholder communication about timeline change
  • Sprint planning to prioritize customer requests
  • 跟进bug修复进度
  • 向利益干系人沟通时间线变更
  • 开展迭代规划以确定客户需求的优先级