From c8462cc4b6176cdd7b993a44bd41c117cf272109 Mon Sep 17 00:00:00 2001 From: garrytan Date: Sun, 1 Nov 2026 16:46:32 +0000 Subject: [PATCH] fix(retro): trim Step 12/13 prose back under the parity skeleton cap Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- retro/SKILL.md | 6 +++--- retro/SKILL.md.tmpl | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/retro/SKILL.md b/retro/SKILL.md index 256ffb2d0..3c6136a1f 100644 --- a/retro/SKILL.md +++ b/retro/SKILL.md @@ -504,7 +504,7 @@ End the section with: `N markers, M with no trigger.` If none: `No shortcut debt ### Step 12: Load History & Compare -Check prior history, shared by every worktree of this repo (substitute the session-reminder date for ``): +Load history (shared across worktrees; `` = session-reminder date): ```bash _RM="$HOME/.claude/skills/gstack/bin/gstack-retro-metrics" @@ -512,7 +512,7 @@ _RM="$HOME/.claude/skills/gstack/bin/gstack-retro-metrics" "$_RM" --history --next "" ``` -`RETRO_PRIOR:` lines are prior snapshots, newest first; a file holding only `{}` is a reservation, not a snapshot. `RETRO_HISTORY_ERROR:` means history is unavailable: tell the user, show its fix, and skip history and the Step 13 save. Otherwise no `RETRO_FILE:` line means a stale helper: skip history and suggest `/gstack-upgrade`. +`RETRO_PRIOR:` lists snapshots, newest first (skip `{}` stubs). On `RETRO_HISTORY_ERROR:` show its fix, skip history and Step 13. No `RETRO_FILE:` otherwise: stale helper; skip history, suggest `/gstack-upgrade`. **If prior retros exist:** Load the most recent one with the same `window` using the Read tool; if none matches, disclose that and skip historical deltas. Calculate deltas for available key metrics and include a **Trends vs Last Retro** section (in `compare` mode use the freshly computed prior period instead): ``` @@ -533,7 +533,7 @@ Deep sessions: 3 → 5 ↑2 After computing all metrics (including streak) and loading any prior history for comparison, draft the tweetable summary and the "3 Things to Improve" items using the format in Step 14, then save a JSON snapshot. The Step 14 narrative must reuse this exact summary and these exact items. `streak_days` is the live **team** streak from Step 11 (0 when broken); put the personal streak in `user_streak_days`. -Step 12 reserved `RETRO_FILE` as `{}`: Read it, then use the Write tool to replace it with this schema: +Read Step 12's reserved `RETRO_FILE`, then Write it with this schema: ```json { "date": "2026-03-08", diff --git a/retro/SKILL.md.tmpl b/retro/SKILL.md.tmpl index 1ec7941f3..9a2bd9167 100644 --- a/retro/SKILL.md.tmpl +++ b/retro/SKILL.md.tmpl @@ -349,7 +349,7 @@ End the section with: `N markers, M with no trigger.` If none: `No shortcut debt ### Step 12: Load History & Compare -Check prior history, shared by every worktree of this repo (substitute the session-reminder date for ``): +Load history (shared across worktrees; `` = session-reminder date): ```bash _RM="{{RUNTIME_ROOT}}/bin/gstack-retro-metrics" @@ -357,7 +357,7 @@ _RM="{{RUNTIME_ROOT}}/bin/gstack-retro-metrics" "$_RM" --history --next "" ``` -`RETRO_PRIOR:` lines are prior snapshots, newest first; a file holding only `{}` is a reservation, not a snapshot. `RETRO_HISTORY_ERROR:` means history is unavailable: tell the user, show its fix, and skip history and the Step 13 save. Otherwise no `RETRO_FILE:` line means a stale helper: skip history and suggest `/gstack-upgrade`. +`RETRO_PRIOR:` lists snapshots, newest first (skip `{}` stubs). On `RETRO_HISTORY_ERROR:` show its fix, skip history and Step 13. No `RETRO_FILE:` otherwise: stale helper; skip history, suggest `/gstack-upgrade`. **If prior retros exist:** Load the most recent one with the same `window` using the Read tool; if none matches, disclose that and skip historical deltas. Calculate deltas for available key metrics and include a **Trends vs Last Retro** section (in `compare` mode use the freshly computed prior period instead): ``` @@ -378,7 +378,7 @@ Deep sessions: 3 → 5 ↑2 After computing all metrics (including streak) and loading any prior history for comparison, draft the tweetable summary and the "3 Things to Improve" items using the format in Step 14, then save a JSON snapshot. The Step 14 narrative must reuse this exact summary and these exact items. `streak_days` is the live **team** streak from Step 11 (0 when broken); put the personal streak in `user_streak_days`. -Step 12 reserved `RETRO_FILE` as `{}`: Read it, then use the Write tool to replace it with this schema: +Read Step 12's reserved `RETRO_FILE`, then Write it with this schema: ```json { "date": "2026-03-08",