weekly-digests

Generates a serial, multi-chapter narrative digest of a project's complete claude-mem history, producing one chapter per ISO week of data. It differs from a single sweeping timeline-report: the timeline is split into per-ISO-week files, and one consecutive subagent runs per week, each receiving the prior week's carry-forward block so the story stays coherent across chapters. The chapter count is not fixed; it equals the number of ISO weeks the timeline covers, so a two-week project yields two chapters and a thirty-week project yields thirty.

The workflow resolves the claude-mem worker port, determines the project name (using the parent project when run inside a git worktree), and fetches the full timeline from the worker's context-inject endpoint into a scratch file. A Python splitter parses date headers, groups days into ISO weeks via date.isocalendar() (Monday-start), and writes one file per week under docs/timeline-weeks/, preserving each day's section verbatim and running a dual-pass sanity check that total observations are conserved. A README index table (Week, Dates, Observations, Sessions, File) is built as an operator roadmap, and the resulting file count becomes TOTAL, which drives the pipeline; empty weeks between active weeks are skipped.

Use it when someone asks for weekly digests, a week-by-week story, a serial timeline, or narrative chapters of a project's history, as opposed to a single report. The heart is a strictly sequential subagent pipeline: for each week in chronological order, a general-purpose subagent is dispatched with a prompt template that includes the source week file, an output digest path, a format key for the observation and session lines and emoji legend, and the prior week's carry-forward. Each digest includes a title, tagline, narrative, threads continued/opened/resolved, a cliffhanger, and a fenced carry-forward block capped at about 350 words with disciplined pruning. Tone rules ask for a sharp third-person narrator that treats recurring codebase components as characters, tracks the user's prompt-register evolution, and, for quiet weeks, treats the silence itself as the story.