- groove-utilities-memory-retrospective
- Use $ARGUMENTS to specify period:
- week
- (default),
- month
- , or
- all
- .
- Outcome
- A period retrospective is output to the conversation: session rating trend, recurring mistake patterns, top learnings captured, and a short workflow health summary. No files are written.
- Acceptance Criteria
- Session ratings trend shown (if
- learned/signals.md
- has data)
- Mistake patterns summarised (from resolved incidents in task backend)
- Top learnings listed by topic (from
- learned/*.md
- dated entries)
- Workflow health summary: one sentence on overall trend
- All output goes to conversation only
- Steps
- Memory path is always
- .groove/memory/
- Determine date range from $ARGUMENTS:
- week
-
- last 7 days (today - 7)
- month
-
- last 30 days
- all
- all available data
Default if absent:
week
Session ratings
— read
.groove/memory/learned/signals.md
if it exists:
Parse table rows matching the date range:
| YYYY-MM-DD | N/5 | context |
Compute: count, average rating, trend (last 3 vs first 3 if enough data)
If no data: note "No session ratings recorded yet"
Mistakes
— query the task backend for resolved incidents under "Groove Memory" → "Mistakes":
beans list --parent
-t bug -s completed for resolved; -s in-progress for open Group by title keywords to identify recurring patterns Count total resolved vs open incidents If no task backend or no data: note "No incidents recorded yet" Learnings — glob .groove/memory/learned/*.md (exclude signals.md ): For each file: read and collect dated entries (
YYYY-MM-DD
headings) within the date range
Group by topic (filename stem)
Count entries per topic; show the most recent bullet per topic as a sample
If no files: note "No learnings captured yet"
Git activity
— run
git log --oneline --since="