daily-log

/daily-log

Evening reflection. Help the user review the day by surfacing what they completed and asking what they learned.

Flow

0. Sync

git -C ${GTD_VAULT:-$HOME/gtd} pull --rebase --autostash 2>&1 | tail -3

If errors, stop and ask the user to resolve before editing daily/.

1. Setup

TODAY=$(TZ=Asia/Tokyo date +%Y-%m-%d)

Path: ${GTD_VAULT:-$HOME/gtd}/daily/{TODAY}.md.

2. Locate today's daily

• If daily/{TODAY}.md doesn't exist: Tell the user: 今日のdaily noteがまだありません。 Ask: 先に /morning で作りますか？ それとも空から始めますか？ (morning / blank / cancel)
  • morning → tell user to run /morning, exit.
  • blank → create a minimal daily from templates/daily.md, continue.
  • cancel → exit.
• If exists: proceed.

3. Surface completed items

Find files in ${GTD_VAULT:-$HOME/gtd}/gtd/finished/ whose frontmatter completed: {TODAY}:

grep -l "^completed: ${TODAY}" ${GTD_VAULT:-$HOME/gtd}/gtd/finished/*.md 2>/dev/null

Display:

✅ 今日完了したこと (N件):
 - {title}
 - {title}
 ...

If none: say 今日完了した next-action はなし。 (don't judge — maybe it was an input-heavy day).

3.5 Pull today's Notion entries

Read ${GTD_VAULT:-$HOME/gtd}/.gtd-config.md. If the file doesn't exist, or its YAML frontmatter has no notion: section, skip 3.5 entirely (no error, no message — go straight to step 4).

Otherwise, for each of the configured keys below, fetch today's content. Skip any individual source silently if its config entry is missing or its MCP call fails (don't block the reflection flow):

A. yarakashi (configured under notion.yarakashi)

Use notion-search with:

• data_source_url: value of notion.yarakashi.data_source_url
• query: "{TODAY}" (the date string, e.g. "2026-04-24")

For each hit, notion-fetch the page and keep only those whose 日付 equals {TODAY}. Extract: タイトル, 内容, 原因, 再発防止策, 深刻度, カテゴリ.

B. good_things (configured under notion.good_things)

Same pattern with notion.good_things.data_source_url. Extract: タイトル, 内容, なぜ良かったか, 次にも活かしたいこと, 嬉しさ, カテゴリ.

C. diary (configured under notion.diary)

The diary tree is structured as <root> → <YYYY年MM月> → <DD日>. Use notion-search with:

• page_url: value of notion.diary.parent_page_id
• query: "{MM}月{DD}日" (e.g. "04月24日"), and also try "{DD}日" as fallback

Pick the hit whose title matches {DD}日 under a month page matching {YYYY}年{MM}月. notion-fetch its body (verbatim text, strip Notion markup).

Display to the user (skip any empty section):

📓 日記 (Notion):
  {body excerpt, up to ~500 chars; show full if shorter}

💥 やらかし反省 (N件):
  - [{カテゴリ}/{深刻度}] {タイトル}
    内容: {内容}
    原因: {原因} / 再発防止策: {再発防止策}

✨ 良かったこと (N件):
  - [{カテゴリ}/{嬉しさ}] {タイトル}
    内容: {内容}
    なぜ: {なぜ良かったか} / 次に活かす: {次にも活かしたいこと}

If all three are empty: say Notionには今日のエントリなし。 and skip the Notion section in step 5.

Remember these values for step 5 — they will be written into a ## Notion振り返り section.

4. Ask for reflection

Cover 3 themes in conversation — NOT as a rigid questionnaire. Engage naturally: react to what the user says, ask one brief relevant follow-up if it surfaces something worth pulling on, then move to the next theme. Accept empty/"skip" as "nothing for this section".

Themes to cover (phrase them in whatever way fits the flow — don't recite these verbatim):

1. ログ・気づき — today's observations, realizations, thoughts
2. やったこと — anything done today worth noting that isn't in the completed-tasks list
3. 明日に回すこと — items rolling to tomorrow, whether tasks or feelings

Guardrails while conversing:

• Stay brief. A short reaction + one follow-up is enough. Don't turn it into therapy.
• Don't interpret or reframe feelings. If the user says "疲れた", acknowledge it plainly — no advice, no encouragement unless asked.
• If step 3.5 surfaced Notion content (日記 / やらかし / 良かったこと), you can gently reference it as context ("日記にも〜って書いてたね") but don't force the user to re-explain it.
• End when the 3 themes are covered or the user signals done (終わり/done/ok).

5. Update daily note

Read daily/{TODAY}.md. Fill in sections:

• Under ## ログ・気づき: append #1 response
• Under ## やったこと:
  • First, a bulleted list of today's completed items (from step 3)
  • Then #2 response as additional lines
• Under ## 明日に回すこと: #3 response

If any Notion content was fetched in step 3.5, append a new ## Notion振り返り section at the end of the file. Only include sub-sections for sources that had content:

## Notion振り返り

### 日記
{body verbatim}

### やらかし反省
- **{タイトル}** ({カテゴリ} / {深刻度})
  - 内容: {内容}
  - 原因: {原因}
  - 再発防止策: {再発防止策}

### 良かったこと
- **{タイトル}** ({カテゴリ} / {嬉しさ})
  - 内容: {内容}
  - なぜ: {なぜ良かったか}
  - 次に活かす: {次にも活かしたいこと}

If a ## Notion振り返り section already exists (re-run), skip writing it — do not duplicate.

Leave the "今日やること" section untouched (it was set by /morning; users can re-check [x] themselves in Obsidian).

6. Offer to stage

Ask: この daily note を git stage しますか？ (y/n). If yes:

git -C ${GTD_VAULT:-$HOME/gtd} add "daily/{TODAY}.md"

Don't commit (let the user batch-commit reflection + other changes later, or skip entirely).

Rules

• Never overwrite existing content in a section. Always append.
• Empty responses are fine. Not every day has insights to log.
• Don't interpret feelings. If the user writes "疲れた", record it as-is; don't offer motivational advice unless asked.
• Don't read any other vault files unless needed to find the completed items.
• Notion is a best-effort augmentation. If MCP is unavailable or a query fails, skip Notion silently — never block the reflection flow.
• Notion content is verbatim. Don't paraphrase 日記 / やらかし / 良かったこと entries — the user wrote them there already.
• Keep it under 3 minutes of user time. This is a reflection habit, not a therapy session.