spark-recipe-topic-timeline

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Recipe: Topic Timeline

方案：主题时间线

For a given project or topic, build a unified chronological narrative by interleaving meeting discussions and email threads. Useful for catching up, briefing someone new, or preparing a status update.

Prerequisite: Read the

use-spark

base skill for command reference and filter syntax.

Access level required: read-only.

针对特定项目或主题，通过整合会议讨论内容与邮件线程，构建统一的按时间顺序排列的叙事内容。适用于跟进项目进度、向新成员介绍情况或准备状态更新报告。

前置条件： 阅读

use-spark

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

所需权限： 只读权限。

Steps

步骤

Step 1: Define the scope

步骤1：定义范围

Ask the user for:

The topic or project name (keywords to search on)
The time range (default to 30 days if unspecified)

向用户确认以下信息：

主题或项目名称（用于搜索的关键词）
时间范围（若未指定，默认近30天）

Step 2: Gather meeting data

步骤2：收集会议数据

bash

spark meetings --filter "subject:topic-keyword newer_than:30d"

If the subject filter misses relevant meetings, broaden:

bash

spark meetings --filter "newer_than:30d"

For each relevant meeting, read the summary:

bash

spark meeting <id>

Pull full detail only for meetings where the topic was a major agenda item:

bash

spark meeting <id> --transcript --notes

Record: date, participants, and the key points related to the topic.

bash

spark meetings --filter "subject:topic-keyword newer_than:30d"

如果主题过滤遗漏了相关会议，可扩大搜索范围：

bash

spark meetings --filter "newer_than:30d"

针对每个相关会议，查看会议摘要：

bash

spark meeting <id>

仅当该主题是会议主要议程时，提取完整细节：

bash

spark meeting <id> --transcript --notes

记录内容：日期、参会人员以及与主题相关的关键点。

Step 3: Gather email data

步骤3：收集邮件数据

bash

spark search "topic keyword"

For threads that are clearly relevant, read the full conversation:

bash

spark thread <id>

If there are specific people associated with the topic, also pull their threads:

bash

spark emails --filter "from:person@co.com subject:keyword newer_than:30d"

Record: date of each message, participants, and the substance.

bash

spark search "topic keyword"

对于明显相关的邮件线程，查看完整对话内容：

bash

spark thread <id>

如果有与主题相关的特定人员，还需提取他们的邮件线程：

bash

spark emails --filter "from:person@co.com subject:keyword newer_than:30d"

记录内容：每封邮件的日期、参与者以及核心内容。

Step 4: Merge into a timeline

步骤4：合并为时间线

Combine all entries (meetings and emails) and sort by date. For each entry:

Date
Channel: Meeting / Email
Participants
What happened: one or two sentences summarizing the key substance

将所有条目（会议和邮件）整合并按日期排序。每个条目包含：

日期
渠道： 会议 / 邮件
参与者
事件内容： 用1-2句话总结核心要点

Step 5: Annotate the timeline

步骤5：为时间线添加注释

Layer on editorial notes:

Mark turning points where direction changed
Flag open threads that don't have a resolution
Note gaps — periods with no activity that might indicate stalled progress

补充编辑说明：

标记转折点：即项目方向发生变化的节点
标注未解决线程：尚未得到结论的讨论
记录空白期：无任何活动的时间段，可能意味着进度停滞

Step 6: Present the timeline

步骤6：展示时间线

Start with a one-paragraph executive summary of where the topic stands now, then present the full timeline oldest-to-newest. End with:

Current status: the latest known state
Open items: anything still unresolved
Next touchpoint: upcoming meeting or pending email that will advance the topic

首先用一段执行摘要说明主题当前的状态，然后按从旧到新的顺序展示完整时间线。最后补充：

当前状态： 已知的最新情况
未完成事项： 所有尚未解决的问题
后续触点： 即将召开的会议或待发送的邮件，用于推进该主题

Tips

小贴士

```
spark search
```
is relevance-ranked and returns full bodies — it's the best starting point for email discovery.
Meeting summaries usually capture the topic well enough. Reserve
```
--transcript
```
for meetings where you need exact quotes or attribution.
For topics that span many months, work in chunks (e.g., month by month) to avoid overwhelming the output.
This pairs well with
```
recipe-decision-tracker
```
— use that recipe when you only need the decision points, and this one when you need the full narrative.
If building this for someone else (e.g., onboarding a new team member), call out any assumed context that an outsider wouldn't have.

```
spark search
```
按相关性排序并返回完整邮件内容，是查找邮件的最佳起点。
会议摘要通常已足够涵盖主题内容。仅当需要精确引用或归属时，才使用
```
--transcript
```
提取完整记录。
对于跨数月的主题，可分块处理（例如按月），避免输出内容过多。
本方案与
```
recipe-decision-tracker
```
搭配使用效果更佳——若仅需决策节点，使用后者；若需完整叙事，则使用本方案。
如果是为他人构建时间线（例如为新成员入职培训），需标注出外部人员不了解的预设背景信息。