spark-recipe-draft-batch

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Recipe: Draft Batch Review

操作指南：草稿批量审阅

Review and finalize multiple pending drafts in a single session. Read context for each, decide whether to edit, keep, or discard.

Prerequisite: Read the

use-spark

base skill for command reference and filter syntax.

Access level required: triage.

在单次会话中审阅并完成多个待处理草稿。查看每个草稿的上下文，决定是编辑、保留还是弃用。

前置要求： 阅读

use-spark

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

所需权限等级： triage

Steps

步骤

Step 1: List all pending drafts

步骤1：列出所有待处理草稿

bash

spark emails Drafts

Review the list of drafts - note subjects, recipients, and dates.

bash

spark emails Drafts

查看草稿列表——记录主题、收件人和日期。

Step 2: Review each draft in context

步骤2：查看每个草稿的上下文

For each draft, read the full thread to understand the context:

bash

spark thread <id>

Check if the conversation has moved on since the draft was created - someone else may have replied, or the topic may be resolved.

针对每个草稿，阅读完整对话线程以了解上下文：

bash

spark thread <id>

检查自草稿创建以来对话是否有新进展——可能已有其他人回复，或话题已解决。

Step 3: Decide on each draft

步骤3：处理每个草稿

For each draft, present the options to the user:

Edit - the draft needs changes before sending:

bash

spark draft --edit <id> --body "Updated content..."
spark draft --edit <id> --subject "Updated subject"

Keep as-is - the draft is ready to send. Note it for the user.

Discard - the draft is no longer needed. Move to trash:

bash

spark action moveToTrash <id>

为每个草稿向用户提供以下选项：

编辑 - 草稿需修改后再发送：

bash

spark draft --edit <id> --body "Updated content..."
spark draft --edit <id> --subject "Updated subject"

保持原样 - 草稿已准备好发送，向用户备注该情况。

弃用 - 草稿已无用处，移至垃圾箱：

bash

spark action moveToTrash <id>

Step 4: Report

步骤4：提交报告

Summarize: "Reviewed N drafts. M edited, K ready to send, L discarded."

总结内容：“已审阅N份草稿。其中M份已编辑，K份可发送，L份已弃用。”

Tips

小贴士

Drafts accumulate when the user starts replies but doesn't finish them. This recipe clears the backlog.
Always read the thread before editing a draft - the context may have changed since it was created.
If a thread has new replies since the draft was created, the draft may be outdated and need rewriting.
```
draft --edit
```
updates the draft in place - it doesn't create a new one.
For drafts that are replies (
```
--reply-to
```
), read the original thread to verify the reply still makes sense.
Run this recipe weekly to prevent draft accumulation.
Discarding via
```
moveToTrash
```
is reversible - the draft can be recovered from trash if needed.

当用户开始回复但未完成时，草稿会堆积。本操作指南可帮助清理积压的草稿。
编辑草稿前务必阅读对话线程——自草稿创建以来上下文可能已发生变化。
如果自草稿创建以来对话线程有新回复，草稿可能已过时，需要重写。
```
draft --edit
```
会直接更新原草稿，不会创建新草稿。
对于回复类草稿（
```
--reply-to
```
），需阅读原始对话线程以确认回复仍有意义。
每周执行本操作指南，避免草稿堆积。
通过
```
moveToTrash
```
弃用草稿是可逆的——若需要，可从垃圾箱恢复草稿。