weekly

A weekly review automates reflection by reading your Obsidian session logs to synthesize topics, extract outcomes, and propose intentions. It determines the Mon–Sun date range, reads all logs for that week, and surfaces patterns like stuck points or energy trends.

Pattern detection in a weekly reflection works by analyzing your session logs to surface focus areas, wins, stuck points, energy trends, and neglected areas. It identifies recurring topics and outcomes across the week to guide better goal planning.

Weekly reflection requires session logs stored in your Obsidian vault to function properly. Without these logs, it cannot extract topics, outcomes, or detect patterns, as the entire synthesis relies on reading your recorded weekly activity.

To set next-week intentions, the review process prompts you for 3 goals after summarizing your week's patterns and insights. It then writes these intentions into a structured weekly audit note with required frontmatter fields for task follow-up.

Yes, after generating a weekly audit note you can optionally save learnings to memory using the /learn command. This ensures your detected patterns and reflection insights persist for future goal planning and task follow-up.

The best way to track stuck points and energy trends is using a weekly review that aggregates your session logs into a structured recap. It automatically surfaces focus areas, wins, and neglected areas to reveal what worked and what felt stuck.