gstack/retro
Jayesh Betala 29c97181cc feat(retro): persist "3 Things to Improve" so the next retro detects follow-through
/retro generated its "3 Things to Improve" as throwaway prose and never wrote
them to the .context/retros/ snapshot. The next run loaded the prior snapshot
for trend comparison but had no structured record of what it recommended, so a
week spent acting on retro feedback (security hardening, dependency bumps) got
mischaracterized as a generic "fix ratio is high" instead of "2 of 3 prior
recommendations addressed."

- Step 13 snapshot schema gains a mandatory `recommendations` array
  ({category, text}), populated from the "3 Things to Improve" items.
- Step 12 reads a prior snapshot's `recommendations` back, classifies each as
  addressed / partial / open against this window's commits, changed files, and
  metrics, and surfaces a "Recommendation follow-through" section. Snapshots
  that predate the field are skipped (backward compatible).
- The "3 Things to Improve" narrative is wired to the persisted array so the
  loop closes.

Repo-scoped retro only; global mode (~/.gstack/retros/) left as a follow-up to
keep this contained to one issue.

Fixes #1834

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-03 11:34:06 +05:30
..
SKILL.md feat(retro): persist "3 Things to Improve" so the next retro detects follow-through 2026-06-03 11:34:06 +05:30
SKILL.md.tmpl feat(retro): persist "3 Things to Improve" so the next retro detects follow-through 2026-06-03 11:34:06 +05:30