Groove Utilities Task Update

This handles task updates across multiple backends (Beans, Linear, GitHub) with a thoughtful constraint: you can't mark anything complete without writing a proper resolution first. It'll read your `.groove/index.md` config to figure out which backend you're using, then append progress notes as dated bullets without clobbering what's already there. The mandatory user confirmation before completion is the kind of guardrail that prevents "oops, I didn't mean to close that" moments at 2am. If you're bouncing between issue trackers or just want consistent task management hygiene enforced at the tool level, this does exactly that without trying to be clever about it.

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

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-utilities-task-update --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-utilities-task-update

Outcome

A task's status, body, or metadata is updated in the configured backend. Progress notes are appended without overwriting existing content. When completing a task, a resolution (Summary of Changes or Reasons for Scrapping) is written to the task body before marking done.

Acceptance Criteria

Specified fields are updated in backend
Existing body content is preserved; new content is appended
Completed tasks have a "Summary of Changes" or "Reasons for Scrapping" section in body
User confirms before task is marked as completed or scrapped