weekly-digests

# Weekly Digests Produce a serial, multi-chapter narrative digest of a project's complete claude-mem history. Differs from `timeline-report` (one long report) — this generates one digest *per ISO week*, with each subagent reading the prior week's carry-forward block so the story stays coherent. **The chapter count equals the number of ISO weeks the timeline covers.** A project with 2 weeks of data produces 2 chapters; one with 30 weeks produces 30. There is no fixed length — count the weeks first, then drive the pipeline off that count. ## When to Use Trigger when the user asks for: - "Weekly digests" - "Week-by-week story" - "Serial timeline" - "Story chapters of [project]" - "Run a digest for each week" - "Continue the story week by week" If the user wants a single sweeping report, use `timeline-report` instead. This skill is for serial chapter format. ## Prerequisites - claude-mem worker running - Project has at least one ISO week of observations (the pipeline degenerates gracefully — even N=1 works) - A clean output directory the user is comfortable writing into **Resolve the worker port** (do this once, reuse `$WORKER_PORT`): ```bash WORKER_PORT="${CLAUDE_MEM_WORKER_PORT:-$(node -e "const fs=require('fs'),p=require('path'),os=require('os');const uid=(typeof process.getuid==='function'?process.getuid():77);const fallback=String(37700+(uid%100));try{const s=JSON.parse(fs.readFileSync(p.join(os.homedir(),'.claude-mem','settings.json'),'utf-8'));process.stdout.writ...