spark-recipe-stakeholder-brief

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Recipe: Stakeholder Brief

方案：利益相关者简报

Given a person's name, compile all recent interactions — meetings and emails — into a relationship brief. Useful before 1:1s, performance reviews, or re-engaging with someone after a gap.

Prerequisite: Read the

use-spark

base skill for command reference and filter syntax.

Access level required: read-only.

给定一个人的姓名，将所有近期互动——会议和邮件——整理成一份关系简报。在一对一沟通、绩效评估或与某人久未联系后重新对接时非常有用。

前提条件： 阅读

use-spark

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

所需访问权限： 只读。

Steps

步骤

Step 1: Look up the person

步骤1：查找人员信息

bash

spark contacts "person name"

Note their email address(es) and any other details.

bash

spark contacts "person name"

记录他们的邮箱地址及其他相关信息。

Step 2: Pull recent email threads

步骤2：提取近期邮件线程

bash

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

Also check emails sent to them:

bash

spark emails --filter "to:person@co.com newer_than:30d"

For the most important threads, read the full conversation:

bash

spark thread <id>

Note open threads (unanswered or pending action) vs. resolved ones.

bash

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

同时查看发送给他们的邮件：

bash

spark emails --filter "to:person@co.com newer_than:30d"

对于最重要的线程，查看完整对话：

bash

spark thread <id>

区分未完结线程（未回复或待执行操作）和已解决线程。

Step 3: Find shared meetings

步骤3：查找共同参与的会议

bash

spark meetings --filter "newer_than:30d"

Scan meeting titles and participant lists for the person. For each relevant meeting, pull the summary:

bash

spark meeting <id>

If the person's contributions or commitments aren't clear from the summary:

bash

spark meeting <id> --transcript --notes

bash

spark meetings --filter "newer_than:30d"

浏览会议标题和参与者列表以找到该人员。对于每个相关会议，提取会议摘要：

bash

spark meeting <id>

如果摘要中未明确显示该人员的贡献或承诺：

bash

spark meeting <id> --transcript --notes

Step 4: Check upcoming events with them

步骤4：查看与他们相关的即将到来的活动

bash

spark events --week

Note any upcoming meetings where this person is an attendee.

bash

spark events --week

记录该人员将参与的所有即将到来的会议。

Step 5: Compile the brief

步骤5：整理简报

Organize into sections:

Contact: name, email, role (if known from context)
Last interaction: date and channel (meeting or email)
Open items: threads awaiting response, commitments not yet fulfilled
Recent topics: what you've discussed across meetings and email (grouped by theme)
Upcoming: any scheduled meetings with them
Key context: notable decisions made together, recurring discussion themes

按以下板块组织内容：

联系方式： 姓名、邮箱、职位（如果上下文已知）
最后互动： 日期和渠道（会议或邮件）
未完成事项： 待回复的线程、尚未履行的承诺
近期话题： 在会议和邮件中讨论过的内容（按主题分组）
即将到来： 与他们预定的所有会议
关键背景： 共同做出的重要决策、反复讨论的主题

Step 6: Present the brief

步骤6：呈现简报

Lead with the most actionable information — open items and upcoming meetings — then provide the fuller context. Flag anything that looks like it needs attention before the next interaction.

先展示最具行动指导性的信息——未完成事项和即将到来的会议——再提供更完整的背景信息。标注出在下一次互动前需要关注的内容。

Tips

提示

This recipe is person-centric, unlike
```
recipe-meeting-prep
```
which is event-centric. Use this when you want to understand the full relationship, not just prep for one meeting.
For people you interact with frequently, narrow the time window to
```
newer_than:14d
```
to keep the brief focused.
For people you haven't spoken to in a while, widen to
```
newer_than:90d
```
or use
```
after:yyyy/MM/dd
```
to capture the last meaningful period.
Use
```
spark search "person name"
```
as a supplementary search to catch threads where they're mentioned but not in the from/to fields.
If the person is a teammate,
```
spark team "Team Name"
```
may show their current email assignments.

本方案以人员为中心，不同于以事件为中心的
```
recipe-meeting-prep
```
。当你想要了解完整的关系情况，而不仅仅是为一场会议做准备时，请使用本方案。
对于频繁互动的人员，可将时间范围缩小至
```
newer_than:14d
```
，以保持简报聚焦。
对于久未联系的人员，可将时间范围扩大至
```
newer_than:90d
```
，或使用
```
after:yyyy/MM/dd
```
来捕捉最后一段有意义的互动时期。
使用
```
spark search "person name"
```
作为补充搜索，以捕捉他们被提及但不在发件人/收件人字段中的线程。
如果该人员是团队成员，
```
spark team "Team Name"
```
可能会显示他们当前的邮件分配情况。