mcpField
G
groove-utilities-task-update

groove-utilities-task-update

github.com/andreadellacorteProductivity6545 installsUpdated 14w ago
Repository

About groove-utilities-task-update

A task-update skill for Groove projects that edits status, body, and metadata in the configured task backend. It preserves existing text, appends dated progress notes, and requires a resolution and explicit confirmation before completion or scrapping.

Key features

  1. 01Updates task status, body, and metadata
  2. 02Appends dated progress notes
  3. 03Preserves existing task body content
  4. 04Requires resolution before completion
  5. 05Requests confirmation before completion

Use cases

  1. 01Record progress on an active task
  2. 02Complete a task with a change summary
  3. 03Scrap a task with documented reasons

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/andreadellacorte/groove --skill groove-utilities-task-update

After installing, type/groove-utilities-task-updatein Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported