prompt-retrolisted

# prompt-retro The meta-loop: the setup studies its own usage and proposes its next improvement. Born from a full-history audit (thousands of human prompts) that found rituals were being codified at rep ~25 instead of rep ~3. This skill makes that audit cheap and recurring, so the gap shrinks to one retro cycle. ## State In this skill dir: - `retro-log.md` — one section per run: date, window, lens, metrics, proposals. Read it first; the current run's window starts where the last one ended. - `briefs/YYYY-MM-DD.md` — the FULL brief of every past run, exactly as delivered. **Read the last 2-3 briefs before writing anything**: they are the record of what the user has already been told. A finding repeated verbatim across briefs is noise; either drop it, or escalate it explicitly ("third retro in a row — this isn't getting fixed, here's why I think that is"). Save the current run's brief here before surfacing it. ## Protocol 1. **Extract.** `python3 "$SKILL_DIR/scripts/extract_prompts.py" <scratch-dir>/digests --since <last-run-date>` — walks every `~/.claude*` config dir, keeps only human-typed prompts (drops task-notifications, hook/judge prompts, harness runs), writes one digest per project with session headers (interrupts, slash-commands) and timestamped prompts. 2. **Fan out analysis agents** (one per major project digest + one quantitative cross-cutting pass), each reporting: - recurring task types prompted by hand (with counts + verbatim examples)