Menu
Update an existing task in the configured backend.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.
Set up task backend and configuration.
Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.
Install groove's Cursor native hooks into .cursor/hooks.json. Enables compaction-safe re-priming, session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.
Run all groove health checks: config, backends, companions, AGENTS.md.
| name | groove-utilities-task-update |
| description | Update an existing task in the configured backend. |
| license | MIT |
| allowed-tools | Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) AskUserQuestion |
| metadata | {"author":"andreadellacorte"} |
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.
tasks.backend from .groove/index.md to determine backendtasks.backend: none, no-op with friendly messagebeans: beans update <id> -s <status> and beans update <id> -d "<body>"linear: update issue via linear CLI or MCPgithub: gh issue edit <number> --body "<body>" and label/close commands