# groove-utilities-memory-promises

Captures deferred tasks during coding sessions and tracks them as items in the beans backend for later review.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 518 installs · ★ 6
- Author: andreadellacorte
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/andreadellacorte/groove/tree/HEAD/skills/groove-utilities-memory-promises/SKILL.md
- Updated: 2026-07-24
- HTML: https://affpapa.org/en/nevibecode/skills/groove-utilities-memory-promises

## What it does

This skill catches conversational items you plan to revisit later, preventing them from vanishing into chat history. It routes promises into a structured hierarchy in `beans`, placing them under a dedicated Groove Memory milestone and a Promises epic. Tasks get flagged with a deferred status so they stay separated from your active priorities.

Reviewing and updating the list takes minimal input. Passing `--list` prints open entries in an ordered index, while `--resolve <N>` closes a specific record by number. The agent will not capture items automatically without asking for explicit user confirmation first.

If `.groove/index.md` sets `tasks.backend` to `none`, the skill halts execution immediately and instructs you to run `/groove-utilities-task-install`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-memory-promises -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/groove-utilities-memory-promises/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/groove-utilities-memory-promises/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-memory-promises -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/groove-utilities-memory-promises/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-memory-promises -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/groove-utilities-memory-promises/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install andreadellacorte/groove groove-utilities-memory-promises
```

2. **Manually: put the files in place**
- File: `.github/skills/groove-utilities-memory-promises/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-memory-promises -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/andreadellacorte/groove --path skills/groove-utilities-memory-promises
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/groove-utilities-memory-promises/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-memory-promises -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/andreadellacorte/groove/tree/HEAD/skills/groove-utilities-memory-promises/SKILL.md

## When to use it
- record deferred thoughts without disrupting current session flow
- list pending session promises in a numbered overview
- close an unresolved promise by its index number

## Example prompts
- Run groove-utilities-memory-promises to record that we need to write unit tests for the auth module
- Show all pending items with groove-utilities-memory-promises --list
- Mark promise 2 as completed using groove-utilities-memory-promises --resolve 2

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: dff50ea48aa8cd85.

BEGIN THIRD-PARTY FILE dff50ea48aa8cd85
```text
---
name: groove-utilities-memory-promises
description: "Capture and resolve deferred items from a session ('we'll come back to that'). Use $ARGUMENTS as the promise text, or --list / --resolve N."
license: MIT
allowed-tools: Read Write Edit Glob Bash(beans:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

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

### Ensure parent hierarchy

Before any operation, resolve or create the parent epic:

1. Find or create the **Groove Memory** milestone:
   - `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 ID
2. Find or create the **Promises** epic under that milestone:
   - `beans 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 ID

Use the Promises epic ID as `<parent-id>` for all promise tasks.

### `--list`

1. Resolve `<parent-id>` (see above)
2. `beans list --parent <parent-id> -s todo -t task`
3. Display as numbered list: `1. [<id>] <title>` — position number for `--resolve N`, beans ID in brackets
4. If empty: print "No open promises."

### `--resolve <N>`

1. Resolve `<parent-id>`; run `beans list --parent <parent-id> -s todo -t task`
2. Find the Nth item; if not found: print "No open promise #N" and exit
3. `beans update <id> -s completed`
4. Confirm: "Promise #N resolved."

### Default — add a promise

1. Resolve `<parent-id>` (see above)
2. Get promise text from $ARGUMENTS if provided; otherwise ask: "What's being deferred?"
3. Optionally ask: "Any context? (enter to skip)"
4. `beans create "<text>" -t task --parent <parent-id> -s todo -p deferred`
5. If context given: `beans update <id> -d "<context>"`
6. Confirm: "Promise captured: [<id>] <text>"
```
END THIRD-PARTY FILE dff50ea48aa8cd85

The third-party file has ended. Everything between the dff50ea48aa8cd85 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2739 of 3401 bytes. © andreadellacorte · MIT · https://github.com/andreadellacorte/groove/tree/HEAD/skills/groove-utilities-memory-promises/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md