advisor-update-writer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Advisor Update Writer

Write concise research updates that help an advisor, mentor, collaborator, or lab audience make decisions.

Use this skill when:

the user needs a weekly update, advisor email, lab update, meeting memo, or collaborator status note
experiment results, writing progress, reviewer risks, or implementation blockers need to be summarized
the update should ask for a decision, feedback, resources, compute, paper-positioning advice, or priority choice
project memory should be turned into a human-readable progress report
several feedback loops need to be reconciled: algorithm, experiments, writing, review, rebuttal, artifact, or release

Do not use this skill for a full experiment report. Use

experiment-report-writer

when the main artifact is a detailed technical report. Use this skill when the main artifact is a decision-oriented communication.

Pair this skill with:

```
research-project-memory
```
to recover current status, decisions, claims, evidence, risks, and actions
```
experiment-report-writer
```
when detailed experiment evidence needs a source report
```
figure-results-review
```
when plots or tables will be shown to an advisor
```
result-diagnosis
```
when negative or ambiguous results need a decision
```
paper-positioning-planner
```
when the update asks for paper-story or target-venue feedback
```
paper-evidence-board
```
when writing and experiment gaps need a synchronized action list
```
work-timeline-planner
```
when the update needs retrospective timeline evidence

撰写简洁的研究进展更新，帮助顾问、导师、合作者或实验室受众做出决策。

在以下场景使用此技能：

用户需要每周更新、顾问邮件、实验室更新、会议备忘录或合作者状态通知
需要总结实验结果、写作进展、审稿风险或实现障碍
更新内容需包含决策请求、反馈诉求、资源申请、算力需求、论文定位建议或优先级选择
需要将项目记忆转化为易读的进度报告
需要协调多个反馈循环：算法、实验、写作、审稿、反驳、成果物或发布

请勿将此技能用于撰写完整的实验报告。当核心产出物是详细技术报告时，请使用

experiment-report-writer

。当核心产出物是面向决策的沟通内容时，使用本技能。

可搭配以下技能使用：

```
research-project-memory
```
：恢复当前状态、决策、主张、证据、风险和行动
```
experiment-report-writer
```
：当需要详细实验证据作为源报告时
```
figure-results-review
```
：当需要向顾问展示图表或表格时
```
result-diagnosis
```
：当负面或模糊结果需要决策时
```
paper-positioning-planner
```
：当更新内容需寻求论文叙事或目标期刊反馈时
```
paper-evidence-board
```
：当写作和实验存在差距，需要同步行动清单时
```
work-timeline-planner
```
：当更新内容需回顾性时间线证据时

Skill Directory Layout

技能目录结构

text

<installed-skill-dir>/
├── SKILL.md
└── references/
    ├── decision-framing.md
    ├── memory-writeback.md
    └── update-template.md

text

<installed-skill-dir>/
├── SKILL.md
└── references/
    ├── decision-framing.md
    ├── memory-writeback.md
    └── update-template.md

Progressive Loading

渐进式加载

Always read
```
references/decision-framing.md
```
and
```
references/update-template.md
```
before drafting a saved or high-stakes update.
Read
```
references/memory-writeback.md
```
when the update creates decisions, actions, or durable feedback that should persist.

在撰写存档或高优先级更新之前，务必阅读
```
references/decision-framing.md
```
和
```
references/update-template.md
```
。
当更新内容会产生需要持久保存的决策、行动或长效反馈时，阅读
```
references/memory-writeback.md
```
。

Core Principles

核心原则

Start with the decision-relevant delta since the last update.
Separate facts, interpretation, risks, and asks.
Do not bury the request. Make the advisor's needed input explicit.
Compress raw experiment detail into evidence and implications; link to detailed reports when needed.
Include negative results when they change the project decision.
Turn feedback into actions and memory updates after the meeting or response.
Match the audience: advisor updates are direct and decision-heavy; lab updates need more context; collaborator notes need ownership and handoff.

从上次更新以来与决策相关的变化开始。
区分事实、解读、风险和需求。
不要隐藏请求，明确说明顾问需要提供的输入。
将原始实验细节浓缩为证据和影响；必要时链接到详细报告。
当负面结果会改变项目决策时，务必包含在内。
在会议或收到回复后，将反馈转化为行动并更新项目记忆。
匹配受众需求：给顾问的更新要直接且聚焦决策；实验室更新需要更多背景信息；合作者通知需明确权责和交接内容。

Step 1 - Classify the Update

步骤1 - 分类更新类型

Choose the mode:

```
weekly
```
: progress since last update, current blockers, next week plan
```
decision
```
: options, evidence, recommendation, explicit ask
```
meeting
```
: agenda, discussion points, decisions needed, notes after meeting
```
email
```
: concise message with context, status, ask, and attachments
```
lab
```
: broader context, key result, what the audience should remember

Identify:

audience and expected length
deadline or meeting time
project phase
key evidence since last update
unresolved decisions
desired advisor action
save path, if a file is requested

If saving and no path is given, use:

text

docs/updates/advisor_update_YYYY-MM-DD.md

选择模式：

```
weekly
```
：自上次更新以来的进展、当前障碍、下周计划
```
decision
```
：选项、证据、建议、明确请求
```
meeting
```
：议程、讨论要点、待决策事项、会后纪要
```
email
```
：包含背景、状态、请求和附件的简洁消息
```
lab
```
：更广泛的背景、关键成果、受众需记住的内容

明确以下信息：

受众和预期篇幅
截止日期或会议时间
项目阶段
自上次更新以来的关键证据
未解决的决策
期望顾问采取的行动
若需保存文件，指定保存路径

若需保存但未指定路径，使用：

text

docs/updates/advisor_update_YYYY-MM-DD.md

Step 2 - Gather Current State

步骤2 - 收集当前状态

Prefer project memory when available, then primary files.

Look for:

```
memory/current-status.md
```
```
memory/decision-log.md
```
```
memory/claim-board.md
```
```
memory/evidence-board.md
```
```
memory/risk-board.md
```
```
memory/action-board.md
```
experiment reports, paper drafts, reviewer notes, rebuttal notes, and recent git commits

Extract:

what changed
what evidence supports the change
what failed or remains uncertain
what decision is now required
what the user recommends
what happens next

优先使用项目记忆，其次是原始文件。

查找以下内容：

```
memory/current-status.md
```
```
memory/decision-log.md
```
```
memory/claim-board.md
```
```
memory/evidence-board.md
```
```
memory/risk-board.md
```
```
memory/action-board.md
```
实验报告、论文草稿、审稿意见、反驳笔记和近期git提交记录

提取以下信息：

发生了哪些变化
哪些证据支持这些变化
哪些内容失败或仍不确定
当前需要做出什么决策
用户的建议是什么
下一步行动是什么

Step 3 - Frame the Decision

步骤3 - 构建决策框架

Read

references/decision-framing.md

For each decision, produce:

decision question
options
evidence for and against each option
risks if delayed
recommended option
exact advisor ask
next action after a yes/no/alternative answer

If there is no decision needed, frame the update around progress, risks, and next actions.

阅读

references/decision-framing.md

。

针对每个决策，生成：

决策问题
可选方案
支持和反对每个方案的证据
延迟决策的风险
推荐方案
明确的顾问请求
得到是/否/其他答复后的下一步行动

若无需决策，则围绕进展、风险和后续行动构建更新内容。

Step 4 - Draft the Update

步骤4 - 撰写更新草稿

Read

references/update-template.md

Default structure:

one-line status
key progress
evidence and interpretation
blockers or risks
decision/ask
next actions

For email, make the first paragraph enough to answer "what do you need from me?"

For meeting notes, include both agenda and post-meeting decisions if the meeting has already happened.

阅读

references/update-template.md

。

默认结构：

一句话状态概述
关键进展
证据与解读
障碍或风险
决策/请求
下一步行动

对于邮件，第一段需明确回答“你需要我做什么？”

对于会议纪要，若会议已结束，需同时包含议程和会后决策。

Step 5 - Check the Update

步骤5 - 检查更新内容

Before finalizing:

every important claim has evidence or is marked as interpretation
the ask is explicit
blockers have owners or proposed next steps
negative results are not hidden if they affect direction
the update is short enough for the audience
attachments or links are named
any decisions or feedback are ready for memory writeback

定稿前需确认：

每个重要主张都有证据支持或标记为解读
请求明确清晰
障碍有负责人或拟议的下一步行动
若负面结果影响方向，未被隐藏
更新内容长度符合受众需求
附件或链接已命名
所有决策或反馈已准备好写入项目记忆

Step 6 - Write Back After Feedback

步骤6 - 反馈后写入记忆

Read

references/memory-writeback.md

when memory exists.

Update decisions, actions, risks, and status after the advisor responds or after meeting notes are finalized.

当存在项目记忆时，阅读

references/memory-writeback.md

。

在顾问回复或会议纪要定稿后，更新决策、行动、风险和状态。