Skip to content
Justin's Obsidian Academy

6. Weekly Review

TL;DR — Sunday evening, say “weekly review”. Claude reads every daily note from the past 7 days, recent project changes, and completed tasks. Produces a single review note in 30-Areas/reviews/ with wins, lessons, themes, missed commitments, and a proposed top-3 for next week.

The point: turn 7 days of operational noise into one signal you’ll actually re-read in 6 months.

When to use it

Section titled “When to use it”
  • Sunday night, before the new week starts
  • After a major project ends — do a project-scoped variant
  • After a hard week, to keep the lessons rather than the bruises
  • Quarterly: stack the four most recent weekly reviews into a quarterly retrospective

You get back a review note with:

  • 🏆 Wins — specific, named (shipped X on Wednesday, not “made progress”)
  • 🪨 Stuck on — items appearing in multiple daily notes without progress
  • 📚 Lessons — quoted insights from your daily logs
  • ⏭️ Missed / dropped — tasks that slipped or commitments to others you didn’t deliver
  • 🔭 Themes — recurring topics — what was this week about?
  • 🎯 Top 3 for next week — picks up dropped commitments + continues strongest theme + adds one growth item

Under the hood

Section titled “Under the hood”
  • Skill location: ~/.claude/skills/weekly-review/SKILL.md
  • Reads:
    • All 10-Daily/YYYY-MM-DD.md matching the week’s range
    • obsidian_get_recent_changes (days=7, limit=50)
    • Vault-wide search for - [x] completed tasks
  • Writes: 30-Areas/reviews/YYYY-[W]WW.md (ISO week number)
  • Doesn’t auto-create: templates use 90-Templates/weekly-review.md

Watch out for

Section titled “Watch out for”
  • Sparse weeks — early weeks have few daily notes. The review will be thinner; that’s accurate.
  • Don’t sanitize the review. If a week was hard, the review should say so. Future-you needs honesty, not polish.
  • Themes ≠ events. One bad day is data; three bad days in a row is a theme. The skill is trained to surface patterns, not anecdotes.
  • Sunday bias — if Sunday is your worst day (errand chaos), do reviews on Saturday morning instead. Block 20 minutes and treat it as sacred.

Make it yours

Section titled “Make it yours”
  • Monthly stack: create monthly-review that reads the last 4 weekly reviews and finds higher-order themes.
  • Custom sections: add Health, Family, Finance subsections — the review surfaces patterns across life areas, not just work.
  • Streaks: include “consecutive weeks reviewed” as a metric. Gamification has its place.
Section titled “Related workflows”
Daily Driver The input. Feed quality in, get quality reviews out.
MOC Maintainer Pairs well — run weekly review then rebuild MOCs