Back to Details

daily-brief

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Daily Brief

每日简报

Produces a 60-second morning briefing. Outputs in a fixed structure so Ane can scan and act without re-parsing formatting every day.
生成一份60秒即可快速浏览的晨间简报。输出采用固定结构，方便Ane无需每天重新解析格式，即可快速浏览并采取行动。

When to use

使用场景

Trigger when the user opens the day, mentions a morning briefing, or asks what today looks like. Do not use for end-of-day summaries — route to 
journal-reflection
for that.
当用户开启新一天、提及晨间简报或询问今日安排时触发。请勿用于每日总结——此类需求请转至
journal-reflection
处理。

Required inputs

必要输入

If no MCP is connected, ask the user for any of these that are missing before producing output. Ask in one batch, not iteratively.
  1. Today's calendar (times, attendees, purpose)
  2. Top 1-3 priorities carried from yesterday or the week plan
  3. Overdue or blocked items (what is stuck, since when)
  4. Decisions pending (what needs a call from Ane, by when, for whom)
  5. Energy state in one word (fresh / tired / scattered / focused)
If calendar MCP or email MCP is available, pull directly instead of asking.
若未连接MCP，需在生成输出前一次性询问用户缺失的以下信息，而非逐一询问：
  1. 今日日程（时间、参会人员、会议目的）
  2. 昨日遗留或本周计划中的1-3项核心优先级事项
  3. 逾期或受阻任务（具体受阻内容、开始受阻时间）
  4. 待决策事项（需要Ane做出何种决策、截止时间、相关对象）
  5. 用一个词描述当前精力状态（精力充沛/疲惫/涣散/专注）
若已连接日历MCP或邮件MCP，则直接调取信息，无需询问用户。

Output format

输出格式

Produce exactly these sections, in this order, each under the named heading:
Top priority today One sentence. The single most important thing. Lead with the verb.
Calendar Chronological list. For each: time, meeting, one-line prep note (who, goal, what Ane owns going in). Skip pure-FYI meetings.
Overdue / blocked Bulleted. For each: what it is, what is blocking it, the next action and owner. Flag any item stuck more than 7 days.
Decisions pending Bulleted. For each: the decision, by when, what Ane needs to decide, what information is missing.
Energy check One sentence matched to the state the user reported. If "scattered", propose the one thing to drop today. If "tired", propose the one meeting to protect and the one to reschedule. If "fresh", propose the hardest thing to front-load.
Data gaps List anything the user did not provide that meaningfully affects the brief. Use the format: 
⚠️ Data gap: [what is missing] — [why it matters] — [recommended action]
. Omit this section if there are no gaps.
严格按照以下顺序生成对应板块，每个板块使用指定标题：
今日核心优先级 一句话表述。唯一最重要的事项。以动词开头。
日程安排 按时间顺序排列列表。每项需包含：时间、会议名称、一行准备提示（参会人员、会议目标、Ane需提前准备的内容）。纯告知性会议可省略。
逾期/受阻任务 项目符号列表。每项需包含：任务内容、受阻原因、下一步行动及负责人。标记受阻超过7天的任务。
待决策事项 项目符号列表。每项需包含：决策内容、截止时间、Ane需做出的决策、缺失的信息。
精力状态检查 根据用户反馈的状态生成一句话内容。若状态为“涣散”，建议今日可暂缓的一件事；若为“疲惫”，建议需优先保障的一场会议及可重新安排的一场会议；若为“精力充沛”，建议优先处理最具难度的事项。
数据缺口 列出用户未提供且对简报有重要影响的信息。格式为：
⚠️ 数据缺口：[缺失内容] — [影响原因] — [建议行动]
。若无缺口则省略此板块。

Writing rules

撰写规则

Follow the house style from CLAUDE.md: active voice, sentences under 25 words, no em-dashes, no hedging, no performative softeners. Lead every line with the actor or the action. No abstract openings.
遵循CLAUDE.md中的规范：使用主动语态，句子长度不超过25词，不使用破折号，不模棱两可，不使用客套性软化表述。每句以行动主体或行动开头，避免抽象开篇。

Limitations

限制条件

Do not invent calendar items, decisions, or blockers. If the user did not provide a section's inputs and no MCP supplies them, leave the section empty and flag it as a data gap. Do not pad.
不得虚构日程事项、决策或受阻任务。若用户未提供某板块的输入且无MCP提供相关信息，则该板块留空并标记为数据缺口。不得随意填充内容。