weekly-review

name	weekly-review
description	Generates weekly review content in Obsidian by reading daily notes, synthesizing completed work, planned tasks, and reflections, then filling the Notes section of the weekly note. Use when asked to "weekly review", "weekly note", "fill in the weekly note", "weekly note を埋めて", "週の振り返り", "今週の振り返り", "週次レビュー", or similar requests about weekly notes.
disable-model-invocation	true
argument-hint	[week e.g. W08]

Weekly Review

Generate a weekly review by reading Obsidian daily notes and synthesizing them into the weekly note's Notes section.

Quick Start

/weekly-review        # Current week (based on ISO week)
/weekly-review W08    # Week 8 of current year
/weekly-review 2026-W08  # Specific year and week

Vault Paths

• Daily notes: 99_Tracking/Daily/YYYY-MM-DD.md
• Weekly notes: 99_Tracking/Weekly/YYYY-WWW.md

Workflow

Step 1: Determine Target Week

Parse $ARGUMENTS:

• W08 -> current year's W08
• 2026-W08 -> as-is
• Empty -> current week via date +%G-W%V

Compute Monday-Sunday dates and prev/next week numbers:

deno run ~/.claude/skills/weekly-review/iso-week.ts YYYY-WNN

Output: 7 lines of dates (Mon-Sun as YYYY-MM-DD), then PREV:YYYY-WNN and NEXT:YYYY-WNN.

Step 2: Load Data (Parallel)

Fetch all of the following in parallel Bash calls using obsidian read:

1. Weekly note: 99_Tracking/Weekly/YYYY-WWW.md -- if not found, print error and abort
2. Previous week: 99_Tracking/Weekly/YYYY-W{prev}.md -- for "next week" carryover; skip if missing
3. Daily notes: Mon-Sun (7 files) -- skip missing days silently

Total: up to 9 files in one parallel call.

Step 3: Collect & Parse Data

Extract from each daily note:

• To-Do (## 📝 To-Do): [x] completed / [ ] incomplete
• Tasks (## 🧑‍💻 Tasks): long-term task items
• Memo (## ✍️ Memo): timestamped entries
  • Project identification: extract repo-name from `(repo-name/short-hash)` pattern
  • Entries without pattern: work-related -> Misc, personal -> material for "feelings" section
• Frontmatter: emotion score (0 may mean "not recorded"; if all days are 0, infer tone from Memo content)

Assess existing weekly note state:

• Bare template: all subsections (0-3) are empty or contain only - tba -> fresh generation (no merge needed)
• Partially filled: 1+ subsections have substantive content -> merge mode
• Always discard - tba placeholder under ## Notes
• ## Analysis: preserve dataviewjs blocks verbatim (never modify)
• ## History / ## Reading: validate and fix in Step 5

Step 4: Synthesize Content

Generate 4 subsections in Japanese:

0.今週やること

• Start from all items in previous week's "来週やること" (carry over even if not seen in daily notes)
• Supplement with this week's To-Do items
• Granularity: task-level (one bullet per planned task). The milestone rollup rules from 1.今週やったこと do NOT apply here
• Merge mode: respect existing content, add only new items; deduplicate against carryover items

1.今週やったこと

• Group completed To-Do [x] items and Memo achievements by project label
• Project labels: use repo names (P&L, dotfiles, concierge-app, etc.) or Misc
• Granularity — human-readable milestone level:
  • Target 5-10 bullets per project, hard cap 10. If exceeding, roll up related items
  • Roll up multi-step workstreams into 1-2 milestone bullets. "A / B / C を個別実装" ではなく「〇〇機能一式を実装（A / B / C）」のように一段抽象化
  • Do NOT emit standalone bullets for: individual RPC names, file paths, PR numbers, commit SHAs, API endpoint names. Embed them as parenthetical details under a milestone bullet only when necessary for disambiguation
  • Sparse projects (1-2 daily mentions only): keep to 1-2 bullets; consider merging into Misc rather than padding
  • Rationale: daily notes often contain Claude Code の自動要約で情報密度が高いため、そのまま箇条書き化すると細粒度になりすぎる。「その週に何をしたか」を人間が 30 秒で把握できる粒度に集約する
• Merge mode: preserve existing manual entries unless they violate the granularity rules above (in which case roll them up first); after rollup, deduplicate (keep the more detailed version)

2.来週やること

• Collect incomplete To-Do [ ] items + Tasks + "next week" mentions from Memo
• Group by project label (same as "今週やったこと"): P&L, concierge-app, dotfiles, Misc, etc.
• Use nested bullet format:

  - P&L
      - ex-proxy のリファクタ（Start/Resume を WS で実装）
      - バックグラウンド切り替え対応
  - Misc
      - FE スキル面接コンテンツの見直し・再設計
  

• Carry over sub-item structure from To-Do where available
• Granularity: task-level (one bullet per planned task). The milestone rollup rules from 1.今週やったこと do NOT apply here
• Merge mode: respect existing content, add only new items

3.感想

• 3-6 bullets total, structured as:
  1. Lead bullet: emotion trend (only days with recorded values, e.g., Mon 6 → Tue 8 → Wed 5 → Thu 7). If all recorded values are 0 (= not recorded), skip this bullet and compensate by adding one more topic bullet so the total still lands in the 3-6 range
  2. 1-4 middle bullets: notable events / pivotal topics of the week (meetings, milestones, decisions, collaborations)
  3. Trailing bullet: overall tone / carry-forward reflection
• Each event / project mention goes into one bullet only — do NOT spread one topic across multiple bullets
• Write in first-person conversational Japanese
• Merge mode: preserve existing reflections, add new insights from daily notes. When existing entries exceed 6 bullets, consolidate down to the structure above during merge

Step 5: Fix History & Reading Dates (Conditional)

Only modify when corruption is detected. This addresses known Templater bugs.

History validation:

• Extract all ### [[YYYY-MM-DD]] dates
• Compare against Mon-Sun dates from Step 1
• Corruption = missing dates, wrong order, or out-of-range dates
• If corrupted -> regenerate 7 entries (Mon-Sun) in correct order
• If valid -> preserve as-is

Reading validation:

• Extract date >= "START" and date <= "END" values
• START must equal Monday, END must equal Sunday
• Corruption = mismatch or inversion (START > END)
• If corrupted -> fix to correct Monday/Sunday values
• If valid -> preserve as-is

Step 6: Rewrite Weekly Note

Before writing, output a brief summary: section counts, major changes, merge/fresh mode.

Use the Write tool to write directly to the vault file path: ~/Documents/Main/99_Tracking/Weekly/YYYY-WNN.md

Why not obsidian create? The CLI escapes ! to \! in content, breaking Obsidian embed syntax (![[...]]) and JS double negation (!!) in dataviewjs blocks. The Write tool bypasses shell escaping entirely.

• Frontmatter: preserve existing values exactly
• ## Notes: Step 4 synthesized content (no - tba)
• ## Analysis: verbatim copy of existing dataviewjs blocks (do NOT paraphrase or modify)
• ## History: Step 5 result (fixed or preserved)
• ## Reading: Step 5 result (fixed or preserved)

Step 7: Open in Obsidian

Use obsidian open path="99_Tracking/Weekly/YYYY-WNN.md" to display the updated weekly note.

Content Style Guidelines

• Generated Obsidian content is written in Japanese
• Use project labels as prefixes: P&L, dotfiles, concierge-app, Misc, etc.
• Bullet points only, no prose paragraphs
• Feelings section uses first-person conversational Japanese
• Missing or sparse Sat/Sun notes are normal (especially when running on Friday)

Granularity

Weekly notes are read by a human scanning "what happened this week" in 30 seconds. Daily notes contain high-density Claude Code auto-summaries (Stop hook claude-memo.ts) that inflate detail when aggregated verbatim — always roll up before emitting.

• Milestone-level rules for 1.今週やったこと and 3.感想: see Step 4's per-subsection guidance (single source of truth)
• 0.今週やること / 2.来週やること stay task-level (one bullet per planned task) — milestone rollup does NOT apply
• When rolling up: prefer "〇〇機能一式を実装（A / B / C）" over three separate bullets listing A, B, C