Groove Utilities Memory Promises

This captures those "we'll come back to that later" moments before they vanish into the void. It stores promises as deferred tasks under a dedicated Groove Memory milestone, keeping them separate from active work but still tracked in your existing task backend. Run it bare to add a promise, use --list to see what's pending, --resolve N to check one off. The hierarchy management is automatic, so you don't create duplicate epics every time. Honest take: it's a narrow tool that does one thing cleanly. If you've ever lost track of side threads during a long session, this gives you a lightweight way to park them without context switching to a full task manager.

skills.sh installs: 518
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-utilities-memory-promises --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-utilities-memory-promises

Use $ARGUMENTS as the promise text if provided, or a flag:

--list: show all open promises
--resolve <N>: mark promise N as resolved

Outcome

Deferred items from a session are captured before they are forgotten, or existing open promises are reviewed and resolved.

Acceptance Criteria

New promise captured with date and optional context
--list shows all open promises clearly numbered
--resolve N marks promise N as resolved

Task backend

Read 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.