Reflect Work Month

Gather work data for that month:

• Find the Month record in plan.json (match Month title)
• Find weeks belonging to this month (via 🗓️ 2026 Months relation)
• Find the work monthly plan in life.json → workMonthlyPlans (match by 🗓️ 2026 Months relation or Month Plan title)
• Find the work monthly recap in summaries.json → workMonthlyRecap (match by month)
• Collect work rocks across the month's weeks (Category is "Work" or has Work Category)
• Collect work weekly retros from retro.json → workWeekly

Compare plan vs. reality:

• Work monthly plan field: Work Plan
• What did Jon intend vs. what actually happened?
• Surface the gaps and wins

Show patterns across weeks:

• Rock completion trends (achieved vs failed vs not ranked)
• Hours/category trends from work weekly summaries (meetings, design, coding, crit, etc.)
• Recurring themes from work weekly retros

Present data grouped by theme, not by week. Identify the natural talking points from the retros and data (e.g., projects, meetings load, coding output, team dynamics, wins). Personal stuff belongs in /reflect-personal-month only — never mix personal into work reflection.

Guide the conversation:

• Start with a month overview grouped by theme, then go deeper where Jon wants
• Ask ONE question at a time
• Be warm but direct
• Keep responses short

Writing the recap:

• Look at the previous month's Work Recap as a style model — short, outcome-focused, narrative sentences, no bullet points, no headers
• Write to Work Recap field in data/summaries.json (monthly recap)
• Do NOT write Work Reflection — Jon writes that himself in Notion
• Always confirm what you're writing and where before editing
• After editing, remind Jon to run yarn push to sync back to Notion