Work Summaries

Automated AI-synthesized work summaries generated from session logs, changelogs, and git history. Each level rolls up summaries from the level below.

Structure

docs/summaries/
  YYYY-MM/                              # Monthly folder (created on-demand)
    daily/daily-YYYY-MM-DD.md           # Previous day's work
    end-of-month/monthly-YYYY-MM.md     # Previous month rollup
    TODO.md                             # Running TODO tracker for the month
  quarterly/quarterly-YYYY-QN.md        # Previous quarter rollup
  yearly/yearly-YYYY.md                 # Previous year rollup

Monthly folders are created on-demand when the daily summary skill runs. Quarterly and yearly summaries remain top-level since they span multiple months.

Schedule

SkillCronRuns AtSummarizes
/generate-daily-summary3 2 * * *2:03 AM dailyPrevious day
/generate-monthly-summary7 2 1 * *2:07 AM on 1stPrevious month
/generate-quarterly-summary11 2 1 1,4,7,10 *2:11 AM on quarter startPrevious quarter
/generate-yearly-summary15 2 1 1 *2:15 AM on Jan 1stPrevious year

Minutes are staggered so that when multiple triggers fire on the same day (e.g., Jan 1st), they execute in the correct order: daily first, then monthly, then quarterly, then yearly.

Data Sources

LevelPrimary SourceFallback (cold start)
Dailydocs/done/YYYY-mon/, docs/changelog/MM-YYYY.md, git logN/A (reads raw sources directly)
Monthlydocs/summaries/YYYY-MM/daily/YYYY-MM-*.mdRaw done files + changelog + git log
Quarterlydocs/summaries/YYYY-MM/end-of-month/monthly-YYYY-MM.md (3 files)Daily summaries for missing months
Yearlydocs/summaries/quarterly/YYYY-QN.md (4 files)Monthly summaries for missing quarters

TODO Tracker

Each monthly folder contains a TODO.md — a running tracker of action items.

How it works

  • The daily summary skill extracts TODOs from session sources and writes them to TODO.md instead of embedding them in daily summaries.
  • New items are added to the Active section with an added date and day-of-week.
  • Progress on existing items is recorded as threaded sub-bullet entries.
  • Completed items are moved to the Completed section with a completed date.
  • At month boundaries, all incomplete Active items are carried to the next month's TODO.md with a (carried from YYYY-MM) annotation.

Entry format

- [ ] Item description (added: 2026-04-01 Wed)
  - 2026-04-02 Thu: Progress update
  - 2026-04-03 Fri: Another update
- [x] Completed item (added: 2026-04-01 Wed, completed: 2026-04-03 Fri)
  - 2026-04-02 Thu: Tested in staging
  - 2026-04-03 Fri: Deployed to production

Content

Every daily summary includes:

  • TL;DR — Executive overview
  • Accomplishments — What got done, grouped by area
  • Key Decisions — Notable decisions with rationale
  • Follow-ups — Items needing future attention
  • Source Links — References to underlying data

Monthly summaries add a TODO Summary linking to the month's TODO tracker. Higher-level summaries add strategic narrative: evolution, milestones, architecture changes, outlook.

Manual Use

All skills accept an optional argument to target a specific period:

/generate-daily-summary 2026-03-31
/generate-monthly-summary 2026-03
/generate-quarterly-summary 2026-Q1
/generate-yearly-summary 2025

Without an argument, each defaults to the previous period (yesterday, last month, etc.).