Conversation Recap to Obsidian

Split the work in three layers:

1. Entry layer = raw work-item capture

   • append a single session recap into the daily note
   • preserve concrete issue / solution / conclusion / key point details
   • act as the source material for later daily and weekly synthesis

2. Daily summary layer = same-day aggregation

   • read the full daily note
   • merge duplicate work threads
   • compress the day into a small number of reusable conclusions

3. Weekly layer = cross-day synthesis

   • merge same-topic work across multiple days
   • rank larger / more complex items first
   • avoid day-by-day流水账

Use scripts when they improve reliability. Do not avoid them just to stay “pure prompt only.”

Daily note target

Default path:

• daily/YYYY/MM/YYYY-MM-DD.md (organized by year and month)
• Users may override the base directory through local config

Mode 1: Session recap mode

Use this when the user has just finished one conversation or one work block and wants to record a new entry instead of refreshing the whole day.

Session recap principle

Create a new item in the daily note as source material for later summaries.

Default entry structure

#### 事项标题 — HH:mm

- **问题**: ...
- **方案**: ...
- **结论**: ...
- **关键点**: ...
- **关联**: [[...]] · [[...]]
- **标签**: #tag-a #tag-b

Session recap guidance

• Prefer one concrete work item per entry.
• If the conversation truly covered multiple unrelated things, either split into 2 entries or name the entry at a higher level.
• Keep each field tight and useful.
• The title should describe the work item, not just say “对话总结”.
• Use tags sparingly; 1-3 strong tags are enough.
• Preserve document hierarchy: session entries belong in the raw entry section of the daily note, and the generated ## 今日总结 block should stay as a higher-level summary section near the end of the note.
• When appending an entry to a daily note that already contains ## 今日总结, insert the new entry before the generated summary block, then refresh the summary if needed.

Mode 2: Daily summary mode

A daily summary is regenerable. It is not an append-only log.

When asked to refresh the daily summary:

1. Read the full daily note.
2. Treat the whole note as usable source material regardless of whether parts were written by a person or another AI/tool.
3. Ignore only the previous generated summary block for this skill to avoid recursive self-copying.
4. Extract the day’s main work items from the note content.
5. Compress them into a concise review section.
6. Replace only the generated summary block.

Default daily output shape

## 今日总结

- 今日主要事项：...
- 核心解决的问题：...
- 关键点：...
- 结论/产出：...
- 相关文档：[[...]] · [[...]]
- 标签：#tag-a #tag-b

Daily writing guidance

• Prefer outcomes over chronology.
• Merge duplicate points.
• If multiple sessions worked on the same thing, describe it once more strongly.
• If there are multiple unrelated threads, mention the top 2-3, not every small action.
• Keep links limited to durable notes or outputs.
• Treat the entire note as evidence; do not downgrade a section just because it was written by another AI/tool.
• Ignore only the current skill's previous generated summary block when refreshing, so the summary does not recursively paraphrase itself.
• Keep the summary compact and high-density rather than long and chatty.

Mode 3: Weekly summary mode

Default path:

• weekly/YYYY/MM/YYYY-MM-DD.md (organized by year and month)

The date is the Sunday of that reporting week.

Weekly summary principle

A weekly report should be organized by work item, not by day.

The correct unit is not “Tuesday” or “Wednesday.” The correct unit is “the import pipeline fix,” “the skill redesign,” “the database migration,” etc.

If one work item spans 3 days, merge those 3 daily notes into one weekly module.

Weekly frontmatter and module structure

Weekly notes should include frontmatter like:

---
word_count: 1234