Back to Details

journal-reflection

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Journal Reflection

日志反思

Structured reflection without the usual journaling bloat. Four modes. Pick one and run it tight.
无冗余内容的结构化反思。提供四种模式，选择其一即可高效完成。

When to use

使用场景

Trigger when the user asks to reflect, review, or capture learning. Not for morning briefings — route to 
daily-brief
for that.
当用户请求进行反思、复盘或记录学习内容时触发。不适用于晨间简报——此类需求请转至
daily-brief
工具。

Mode selection

模式选择

Ask once, in one prompt, which mode applies. Default to end-of-day if the user says "journal" without specifying.
  1. End-of-day (5 min): today in 3 questions
  2. End-of-week (15 min): week in 5 questions plus a pattern scan
  3. Decision review: one past decision in 4 questions
  4. Learning log: one new framework or concept, linked to what Ane already knows
通过一次提问确认适用模式。若用户仅提及“journal”未指定模式，默认使用每日复盘模式。
  1. 每日复盘（5分钟）：3个问题梳理当日情况
  2. 每周复盘（15分钟）：5个问题加模式扫描梳理本周情况
  3. 决策复盘：4个问题回顾某一项过往决策
  4. 学习日志：记录某一新框架或概念，并关联Ane已掌握的知识

Prompts by mode

各模式提问话术

End-of-day

每日复盘

Ask these three, one at a time, waiting for each answer:
  1. What got done today that mattered? (not a task list — what moved)
  2. What got in the way, and what did it cost?
  3. What does tomorrow need from you that today did not get?
Close with: one commitment for tomorrow, one sentence, verb-first.
依次提出以下三个问题，等待用户逐一回答：
  1. 今日完成了哪些关键事项？（不是任务清单——而是真正推动进展的内容）
  2. 遇到了哪些阻碍？造成了什么影响？
  3. 明日需要完成哪些今日未处理的事项？
结尾要求：用一句以动词开头的话，明确明日的一项承诺。

End-of-week

每周复盘

Ask these five, one at a time:
  1. Against this week's stated goals, what is the honest progress? (percentage-free language)
  2. What patterns showed up this week that also showed up last week?
  3. What did you learn about the work, or about yourself doing the work?
  4. What will you change next week? Specific, small, testable.
  5. What deserves to be named as a win that you have not named yet?
Close with: one pattern-to-watch next week.
依次提出以下五个问题：
  1. 对照本周既定目标，实际进展如何？（避免使用百分比表述）
  2. 本周出现了哪些与上周重复的模式？
  3. 你在工作中或自身工作状态上学到了什么？
  4. 下周你会做出哪些具体、微小且可验证的改变？
  5. 有哪些未被你认可的成果值得被明确为胜利？
结尾要求：指出一个下周需要关注的模式。

Decision review

决策复盘

Ask:
  1. What was the decision, and when did you make it?
  2. What did you know at the time, and what were you guessing?
  3. What happened in the days or weeks since?
  4. What would you do differently if the decision arrived today?
Close with: one rule to carry forward, written as an if-then.
提出以下问题：
  1. 当时做出的是什么决策？决策时间是何时？
  2. 决策时你已知哪些信息？哪些是猜测的内容？
  3. 决策后的几天或几周内发生了什么？
  4. 如果现在面临同样的决策，你会怎么做？
结尾要求：总结一条可沿用的规则，用“如果……那么……”的句式表述。

Learning log

学习日志

Ask:
  1. What is the concept or framework? Cite author and year if it has one.
  2. What problem does it solve that older frameworks do not?
  3. How does it connect to something Ane already uses?
  4. Where will Ane apply it first?
提出以下问题：
  1. 该概念或框架是什么？若有作者和年份请注明。
  2. 它解决了哪些旧框架无法解决的问题？
  3. 它与Ane已在使用的内容有何关联？
  4. Ane会首先将其应用在何处？

Output format

输出格式

Write Obsidian-compatible markdown with YAML frontmatter:
yaml
---
date: YYYY-MM-DD
type: [daily | weekly | decision-review | learning-log]
tags: [journal, ...domain tags]
dg-publish: false
---
Use 
[[wiki-links]]
for people, concepts, frameworks, and projects. Default 
dg-publish
to false. If the user says the note is publishable, set to true and ask for the permalink stub.
Body structure: one H2 per prompt, the answer as plain prose under it, no bullets unless the content is a list.
生成带YAML前置元数据的Obsidian兼容markdown：
yaml
---
date: YYYY-MM-DD
type: [daily | weekly | decision-review | learning-log]
tags: [journal, ...domain tags]
dg-publish: false
---
对人物、概念、框架和项目使用
[[wiki-links]]
格式。默认
dg-publish
设为false。若用户表示笔记可发布，则将其设为true并请求永久链接后缀。
正文结构：每个问题对应一个H2标题，答案以普通 prose 格式置于标题下方，除非内容本身是列表，否则不使用项目符号。

File placement

文件存储位置

If filesystem MCP to 
MELdigitalgarden
is connected:
  • End-of-day: 
    src/site/notes/Journal/Daily/YYYY-MM-DD.md
  • End-of-week: 
    src/site/notes/Journal/Weekly/YYYY-Www.md
  • Decision review: 
    src/site/notes/Journal/Decisions/YYYY-MM-DD-<slug>.md
  • Learning log: 
    src/site/notes/Journal/Learning/<slug>.md
If MCP is not connected, return the markdown as an artifact and name the target path so the user can save it manually.
若已连接至
MELdigitalgarden
的文件系统MCP：
  • 每日复盘：
    src/site/notes/Journal/Daily/YYYY-MM-DD.md
  • 每周复盘：
    src/site/notes/Journal/Weekly/YYYY-Www.md
  • 决策复盘：
    src/site/notes/Journal/Decisions/YYYY-MM-DD-<slug>.md
  • 学习日志：
    src/site/notes/Journal/Learning/<slug>.md
若未连接MCP，则返回markdown内容作为结果，并告知目标存储路径，供用户手动保存。

Writing rules

写作规则

Follow CLAUDE.md house style. One exception: in journal answers, passive and reflective phrasing is acceptable when Ane's answer is itself reflective. Do not rewrite her words into active voice — preserve her voice exactly.
遵循CLAUDE.md的风格规范。唯一例外：在日志回答中，当Ane的回答本身具有反思性时，可使用被动和反思性措辞。不得将她的表述改写为主动语态——需完全保留她的语气。

Limitations

限制条件

Do not invent reflections. Do not auto-answer the prompts. Prompts go to the user and wait. If the user skips a prompt, mark the section 
(skipped)
and move on. Do not lecture.
不得虚构反思内容。不得自动回答问题。需将问题发送给用户并等待回答。若用户跳过某一问题，标记该部分为
(skipped)
后继续。不得进行说教。