andreadellacorte/groove

groove-utilities-task-update

Update an existing task in the configured backend.

First seen Mar 3, 2026

Installation

$ npx skills add andreadellacorte/groove --skill groove-utilities-task-update

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from andreadellacorte/groove · top by installs.

npx skills add andreadellacorte/groove

Browse all from andreadellacorte/groove

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Allowed toolsRead Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) AskUserQuestion
More metadata
author
andreadellacorte

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,521 B
  • docs SUMMARY.md 83 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 539 installs

SKILL.md

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

Constraints

  • Read tasks.backend from .groove/index.md to determine backend
  • If tasks.backend: none, no-op with friendly message
  • Never mark a task completed without a resolution section in the body
  • Ask user to provide resolution if task body has none
  • User must explicitly confirm completion — do not auto-complete
  • Progress notes should be appended as dated bullets under a "Progress" section
  • Backend mappings:

- beans: beans update <id> -s <status> and beans update <id> -d "<body>" - linear: update issue via linear CLI or MCP - github: gh issue edit <number> --body "<body>" and label/close commands