monthly-review

name: monthly-review description: Monthly deep analysis and trend review. Triggers on "monthly review", "month summary", "summarize the month", "what happened in January", or similar requests for monthly summaries.

Monthly Review

Deep monthly analysis — every day, every week, experiments, domain progress, goals.

Workflow

digraph monthly {
  "Determine month" -> "Deep scan daily logs";
  "Deep scan daily logs" -> "Scan ALL referenced files";
  "Scan ALL referenced files" -> "Load weekly reviews";
  "Load weekly reviews" -> "Load experiments & domains";
  "Load experiments & domains" -> "Deep analysis";
  "Deep analysis" -> "Write review";
  "Write review" -> "Save + update docs";
}

1. Determine Month

• If user specified a month → use that
• If not → previous month (not current — it's incomplete)

2. Deep Scan Daily Logs

Load EVERY daily log for the month:

logs/daily/YYYY-MM/YYYY-MM-DD.md  (all days)

For each log extract:

• YAML metrics (all tracked fields)
• Notes (what happened)
• AI Observations
• References to external files

3. Scan ALL Referenced Files (CRITICAL!)

For EVERY daily log, check references:

• Experiment files → load progress
• Research files → load key findings
• Medical records → load results
• Domain notes → load context

This is the key difference from weekly review — monthly goes deeper, loads EVERYTHING relevant from that month.

4. Load Additional Context

5. Deep Analysis

A. Metrics (full month):

B. Weekly Trends:

• W01 vs W02 vs W03 vs W04 — what changed over the month?

C. Activity:

• Total workouts/exercise sessions
• Average steps/day (if tracked)
• Rest days vs active days

D. Experiments:

• Which ran during this month?
• Results, progress, metrics
• Anything to evaluate or end?

E. Domain Progress:

• Which domains changed?
• New research files created
• New insights discovered
• Domain status at end of month

F. Goals Check:

• Compare with goals from me.md and watchlist.md
• What was accomplished?
• What wasn't, and why?

G. Long-term Trends:

• Comparison with previous months (if available)
• Seasonal patterns
• Major changes (weight, lifestyle, treatment)

H. Anomalies & Patterns:

• Outlier days (best, worst)
• Recurring patterns
• Cross-domain correlations
• Things invisible at daily/weekly level

6. Write & Save

Save as logs/monthly/YYYY-MM.md

Structure (AI generates, not rigid):

1. Executive Summary (5-7 sentences)
2. Key Numbers (table)
3. Weekly Trends
4. Activity & Exercise
5. Experiments
6. Health & Symptoms
7. Domain Progress
8. Goals Review
9. Patterns & Insights
10. Recommendations for Next Month

7. Post-Review Updates

After writing the review, ALWAYS check:

• Update me.md? (new baselines, changes)
• Update watchlist.md? (completed/missed items)
• Update any domain? (new insights)
• Update PLAN.md? (milestone completed)

At the end, ask the user:

• Do you agree with the summary?
• Anything to add or correct?
• What priorities for next month?

Arguments

/monthly-review january → review for January /monthly-review 2026-01 → review for January 2026 /monthly-review → previous month