weekly-review

A weekly retrospective consolidates your activity log, inbox, friction log, and insights into an actionable next-week plan. It prompts you for specific process changes and learnings, then writes the structured review directly to your notes repository.

Automating a recurring weekly review involves reading prior notes to ground your reflection in real evidence, capturing friction and learnings through targeted prompts, and writing the output to a structured markdown file for consistent backlog planning.

A skills audit inventories your existing skills and checks usage signals to decide whether to keep, merge, or prune inactive ones. This review process triggers conditionally on a recurring schedule, specifically every fourth weekly review.

Yes, you can use your friction log and inbox to plan actionable process changes. The review workflow reads these files to identify ongoing issues, prompts you for targeted solutions, and updates the logs to ensure your repository improves over time.

The weekly review workflow requires specific notes files located under a ./notes/ directory, including your activity log and friction log. It conditionally writes the generated retrospective output as a markdown file formatted YYYY-WW.md inside notes/reviews/.

A weekly review should capture friction, actionable process changes, learnings, and nagging issues to prevent losing track of progress. By consolidating these signals with prior reviews, it creates a clear momentum plan for the upcoming week.