groove-utilities-memory-mistakes
Use $ARGUMENTS as the mistake description if provided (e.g.
--list
to show open incidents only).
Outcome
The workflow mistake is logged, its root cause is fixed in the relevant memory or learned file, and the lesson is graduated to
.groove/memory/learned/.md
. The incident is closed.
Acceptance Criteria
Incident is recorded with root cause and fix
Permanent fix applied to
.groove/memory/learned/.md
Incident marked resolved
Task backend
Read
tasks.backend
from
.groove/index.md
. Incidents are tracked as tasks in the configured backend. If no task backend is configured (
tasks.backend: none
), tell the user to run
/groove-utilities-task-install
first.
Incidents are stored as bugs under a shared "Groove Memory" milestone → "Mistakes" epic.
Ensure parent hierarchy
Before any operation, resolve or create the parent epic:
Find or create the
Groove Memory
milestone:
beans list -t milestone --search "Groove Memory" -q
— if non-empty, use first ID; otherwise
beans create "Groove Memory" -t milestone
Find or create the
Mistakes
epic under that milestone:
beans list -t epic --parent --search "Mistakes" -q
— if non-empty, use first ID; otherwise
beans create "Mistakes" -t epic --parent
--list
Resolve
beans list --parent -t bug -s in-progress
Display as numbered list:
1. []
If empty: print "No open incidents."
Log and resolve an incident
Resolve
Get description from $ARGUMENTS or ask: "What mistake did I make?"
Ask: "Root cause — why did it happen?" (propose from context; user confirms)
Ask: "What fix should be applied?" (propose; user confirms)
beans create "" -t bug --parent -s in-progress
Apply the fix immediately (edit the relevant file)
Ask: "Which learned topic? (e.g.
anti-patterns
,
tools
)" — suggest based on root cause
Append lesson to
.groove/memory/learned/.md
under
YYYY-MM-DD
heading
beans update -s completed
Report: "Incident resolved → learned/.md"
Constraints
Read
tasks.backend
from
.groove/index.md
; memory path is always
.groove/memory/
Requires a configured task backend — if
tasks.backend: none
, prompt user to install one
Never auto-create incidents without user confirmation
Root cause is required before resolving — do not skip the audit step
Parent hierarchy is idempotent — always check before creating
If the fix targets a
skills/
file: note that
skills/
is managed by groove:update; redirect fix to
learned/anti-patterns.md