spark-recipe-meeting-prep

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Recipe: Meeting Prep

方案：会议准备

Prepare for an upcoming meeting by gathering calendar context, relevant email threads, and attendee information. Optionally, run a gap analysis after the meeting to flag verbal commitments without a written trail and open threads that weren't raised.

Prerequisite: Read the

use-spark

base skill for command reference and filter syntax.

Access level required: read-only.

通过收集日历信息、相关邮件线程和参会者信息，为即将到来的会议做准备。会议结束后可选择性进行差距分析，标记无书面记录的口头承诺以及未被提出的未解决讨论线程。

前置要求： 阅读

use-spark

基础技能文档，了解命令参考和过滤语法。

所需访问权限： 只读。

Steps

步骤

Step 1: Check the calendar

步骤1：查看日历

bash

spark events --today

Identify the meeting to prepare for - note the topic, time, and attendees.

bash

spark events --today

确定要准备的会议——记录会议主题、时间和参会者。

Step 2: Search for relevant email context

步骤2：搜索相关邮件上下文

bash

spark search "meeting topic or project name"

This returns up to 20 emails with full bodies, sorted by relevance. Read the most relevant threads for context.

bash

spark search "meeting topic or project name"

此命令最多返回20封包含完整正文的邮件，按相关性排序。阅读最相关的邮件线程获取上下文信息。

Step 3: Look up attendees

步骤3：查找参会者信息

bash

spark contacts "attendee name"

Repeat for each attendee to gather their email and any other details.

bash

spark contacts "attendee name"

为每位参会者重复执行此命令，收集他们的邮箱及其他相关详情。

Step 4: Check recent correspondence with attendees

步骤4：查看与参会者的近期通信

bash

spark emails --filter "from:attendee@co.com newer_than:14d"

Review any recent threads with the meeting participants for open items or unanswered questions.

bash

spark emails --filter "from:attendee@co.com newer_than:14d"

查看与会议参与者的近期线程，寻找未完成事项或未答复的问题。

Step 5: Flag unresolved threads to raise in the meeting

步骤5：标记需在会议中提出的未解决线程

Check for open or unreplied threads with the attendees that may be worth bringing up:

bash

spark emails --filter "from:attendee@co.com is:unreplied newer_than:14d"
spark emails --filter "to:attendee@co.com is:unreplied newer_than:14d"

Note any threads that look relevant to the meeting topic but haven't been resolved — these are candidates to raise during the discussion.

检查与参会者之间的未回复或未解决线程，确定哪些值得在会议中提出：

bash

spark emails --filter "from:attendee@co.com is:unreplied newer_than:14d"
spark emails --filter "to:attendee@co.com is:unreplied newer_than:14d"

记录与会议主题相关但尚未解决的线程——这些是会议讨论中可提出的候选事项。

Step 6: Present the prep summary

步骤6：呈现准备总结

Summarize for the user:

Meeting: time, title, attendees
Context: key points from relevant email threads
Open items: unanswered questions or pending actions from recent correspondence
Threads to raise: unreplied or unresolved threads with attendees that relate to the meeting topic
Attendees: contact details for reference

为用户总结以下内容：

会议信息： 时间、标题、参会者
上下文： 相关邮件线程中的关键点
未完成事项： 近期通信中的未答复问题或待执行动作
需提出的线程： 与参会者之间未回复或未解决且与会议主题相关的线程
参会者信息： 供参考的联系方式

Step 7 (optional, post-meeting): Meeting–email gap analysis

步骤7（可选，会后）：会议-邮件差距分析

After the meeting, compare what was discussed against the email record to catch gaps. This step requires the meeting transcript to be available.

Read the transcript:
bash
```
spark meeting <id> --transcript --notes
```
Extract topics discussed, commitments made, and decisions reached.
For each major topic, check whether it has an email trail:
bash
```
spark search "topic from meeting"
```
Flag two kinds of gaps:

Discussed in meeting, no email trail — verbal commitments or decisions that may need a follow-up email to create a written record.

Open email threads not raised in meeting — compare the unreplied threads from Step 5 against what was actually discussed. Flag any that seem relevant but weren't mentioned.

Present gaps neutrally — not every gap needs action. Some things are intentionally verbal-only, and some threads are intentionally deferred.

会议结束后，将讨论内容与邮件记录进行对比，找出差距。此步骤需要会议转录文本可用。

读取转录文本：
bash
```
spark meeting <id> --transcript --notes
```
提取讨论的主题、做出的承诺以及达成的决策。
针对每个主要主题，检查是否有邮件记录：
bash
```
spark search "topic from meeting"
```
标记两类差距：

会议讨论过但无邮件记录——口头承诺或决策可能需要跟进邮件以创建书面记录。

未在会议中提出的未解决邮件线程——将步骤5中的未回复线程与实际讨论内容对比，标记相关但未被提及的线程。

以中立方式呈现差距——并非所有差距都需要采取行动。有些内容特意仅以口头形式沟通，有些线程则被有意延后处理。

Tips

提示

Run this 15-30 minutes before the meeting for fresh context.
Use
```
spark search
```
rather than
```
spark emails
```
for topic-based context - search returns full bodies.
If the meeting is recurring, check
```
spark meetings --filter "subject:meeting-topic"
```
for past transcripts.
For large meetings, focus on the 2-3 most important attendees rather than looking up everyone.
The
```
is:unreplied
```
filter is especially useful for surfacing threads that may have been forgotten — both before the meeting (things to raise) and after (things that were missed).
For recurring meetings, running the post-meeting gap analysis regularly can reveal patterns where the same threads go unaddressed week after week.

在会议前15-30分钟执行此流程，获取最新的上下文信息。
如需基于主题的上下文，使用
```
spark search
```
而非
```
spark emails
```
——搜索会返回完整邮件正文。
如果是周期性会议，可使用
```
spark meetings --filter "subject:meeting-topic"
```
查看过往转录文本。
对于大型会议，重点关注2-3位最重要的参会者，而非查找所有参会者的信息。
```
is:unreplied
```
筛选器对于发现可能被遗忘的线程特别有用——无论是会前（需提出的事项）还是会后（遗漏的事项）。
对于周期性会议，定期执行会后差距分析可发现同一线程每周都未得到解决的规律。