Analyze accumulated bug fix cases and propose updates to the self-testing checklist. Use periodically (weekly/monthly) to evolve quality checks based on real issues.
Read .claude/skills/1k-retrospective/references/case-studies.md. Count cases since the last <!-- Retrospective completed --> marker. If fewer than 3 new cases, report "Not enough new cases" and stop.
For each case, extract root cause category and which self-testing section (1-8) could have caught it, or "NEW" if not covered. Aggregate counts per pattern.
Output a short report:
Retrospective — YYYY-MM-DD
Cases analyzed: N (date range: YYYY-MM-DD to YYYY-MM-DD)
Recurring patterns: [pattern] N (NEW/WEAK), [pattern] N (NEW/WEAK)
Proposed changes: Add [Section N] [one-line check] / Strengthen [Section N] [current → revised]
Housekeeping: archive candidates [list], zero-hit checks [list]
Rules when modifying self-testing.mdc:
references/patterns.md[ARCHIVED] prefixAppend to case-studies.md:
<!-- Retrospective completed: YYYY-MM-DD | Cases analyzed: N | Changes applied: N -->
5 cases: 3 BigNumber (NaN/precision/division), 1 cleanup, 1 stale closure. → BigNumber = NEW (3 hits) → Add one-line check to Section 1.