skills/groove-utilities-memory-promises/SKILL.md
Capture and resolve deferred items from a session ('we'll come back to that'). Use $ARGUMENTS as the promise text, or --list / --resolve N.
npx skillsauth add andreadellacorte/groove groove-utilities-memory-promisesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use $ARGUMENTS as the promise text if provided, or a flag:
--list: show all open promises--resolve <N>: mark promise N as resolvedDeferred items from a session are captured before they are forgotten, or existing open promises are reviewed and resolved.
--list shows all open promises clearly numbered--resolve N marks promise N as resolvedRead tasks.backend from .groove/index.md. Promises 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.
Promises are stored as tasks under a shared "Groove Memory" milestone → "Promises" epic hierarchy. This keeps them organised and out of the main work task list.
Before any operation, resolve or create the parent epic:
beans list -t milestone --search "Groove Memory" -q — if output is non-empty, use the first ID; otherwise beans create "Groove Memory" -t milestone and capture the new IDbeans list -t epic --parent <milestone-id> --search "Promises" -q — if non-empty, use first ID; otherwise beans create "Promises" -t epic --parent <milestone-id> and capture the new IDUse the Promises epic ID as <parent-id> for all promise tasks.
--list<parent-id> (see above)beans list --parent <parent-id> -s todo -t task1. [<id>] <title> — position number for --resolve N, beans ID in brackets--resolve <N><parent-id>; run beans list --parent <parent-id> -s todo -t taskbeans update <id> -s completed<parent-id> (see above)beans create "<text>" -t task --parent <parent-id> -s todo -p deferredbeans update <id> -d "<context>"tasks.backend from .groove/index.md at the start of every invocationtasks.backend: none, prompt user to install one-s todo for open, -s completed for resolved; -p deferred to signal not active work--resolve-all--resolve-all requires confirmation: "Resolve all N open promises?" before proceedingtesting
Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.
data-ai
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
documentation
Document lessons, update rules/templates/docs. Use to capture learnings after review.
development
Set up task backend and configuration.