obsidian-daily-reflection-boundaries

name	obsidian-daily-reflection-boundaries
description	Refactor an Obsidian daily workflow so assistant-generated structure is clearly separated from user-written reflection, with ToDo as long-term task hub and daily execution in separate files.

When to use

Use when a user wants help restructuring an Obsidian daily workflow involving:

• ToDo.md as a long-term task center
• separate daily execution pages (e.g. 今日安排)
• Daily Reflections that must preserve a clearly separate user-owned writing space
• avoiding assistant overreach into personal reflection / feelings sections

Boundary

This skill defines structural boundaries for Daily Reflection and ToDo architecture.

It owns:

• assistant/user separation inside Daily Reflection
• distinguishing long-term task hub vs daily execution pages
• keeping personal reflection areas user-owned unless explicitly requested

It does NOT own:

• full Vault-wide state sync after real-world publication or task completion
• turning user reflection into publish-ready notes or media packages
• multi-platform content production and publishing operations

If the task is about syncing reality into ToDo.md, Direction/, project pages, or creating publishable note packages, use vault-state-sync-and-note-publishing.

Core principle

Never prefill or ghostwrite the user's personal reflection area unless explicitly asked.

For daily reflection notes, use a two-block structure:

1. Assistant-owned structured synthesis block at the top
2. User-owned raw notes / feelings block below

This prevents mixing system-generated summaries with the user's authentic journal voice.

Recommended vault architecture

Use this chain: Daily Reflections → Direction → ToDo / project page → 今日安排

Roles:

• Direction/: long-term judgment and signal interpretation
• ToDo.md: long-term task center, not daily schedule
• Other/前进机制/今日安排/YYYY-MM-DD.md: actual daily execution plan
• Daily Reflections/YYYY-MM-DD.md: reality, reflection, and system write-back

Recommended Daily Reflection template

Use headings like:

A. 安比整理区

1. 今天发生了什么（结构化）

2. 现实信号 / 判断更新

3. 卡点 / 摩擦

4. 输出到系统

5. 明日唯一推进点

---

B. 我的原始记录（只留给我自己）

今天实际发生了什么

我的感受 / 心得

Important:

• Only fill section A unless the user explicitly asks for help with section B.
• Leave section B blank for the user.
• If you previously filled section B, correct it immediately.

ToDo refactor pattern

When converting a mixed todo list into a long-term task center:

• remove emphasis on daily scheduling states as the primary top-level structure
• group by function instead:
  • current highest-value items
  • long-term projects / themes
  • ongoing reminders / mechanisms
  • completed / archive
• for important items, add:
  • current status
  • next action
  • blocker
  • completion definition

This makes the task hub usable for long-term steering while keeping daily scheduling elsewhere.

Implementation steps

1. Read existing ToDo.md, recent Daily Reflections, and any daily schedule file.
2. Identify whether the user's problem is really structure confusion between:
   • long-term tasks
   • daily execution
   • reminders/mechanisms
   • personal reflection
3. Create or update a reusable Daily Reflection template with explicit assistant/user boundary.
4. Refactor ToDo.md into a long-term task hub.
5. If relevant, migrate the current day's Daily Reflection into the new two-block format.
6. If the workflow affects long-term direction, add a concise entry to the Direction signal page.
7. Verify the files after writing.

Common pitfall

Do not treat “我的感受 / 心得” as material the assistant should draft by default. Users may see this as intrusive even if the structure is otherwise helpful.

Verification checklist

Before finishing:

• Did Daily Reflections clearly separate assistant content from user-owned writing?
• Did ToDo.md stop acting like a daily schedule?
• Is daily execution located in a separate file?
• Were any overreaching assistant-written personal sections removed?
• Were updated files re-read to verify the final state?