CalvinBackup/gstack
1
0 Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-11-03 15:27:56 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix(retro): trim Step 12/13 prose back under the parity skeleton cap

Browse Source 
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
garrytanandcapy-ai[bot] committed 2026-11-01 16:46:32 +00:00
1 parent 99f7f7c8be
commit c8462cc4b6
2 files changed
+6 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

retro/SKILL.md
+3 -3
View File
@@ -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 `<today>`):
Load history (shared across worktrees; `<today>` = 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 "<today>"
```
`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",
retro/SKILL.md.tmpl
+3 -3
View File
@@ -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 `<today>`):
Load history (shared across worktrees; `<today>` = 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 "<today>"
```
`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",