andreadellacorte/groove-utilities-task-update
skills/groove-utilities-task-update/SKILL.md
Update an existing task in the configured backend.
$ install --global
skillsauthnpx skillsauth add andreadellacorte/groove groove-utilities-task-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:33 PM0.4s1 file scanned
SKILL.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
- author:
- andreadellacorte
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.backendfrom.groove/index.mdto 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>andbeans update <id> -d "<body>"linear: update issue via linear CLI or MCPgithub:gh issue edit <number> --body "<body>"and label/close commands
Related Skills
andreadellacorte/groove-utilities-stats
testing
VerifiedTrustedCommunity
Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.
5SKILL.mdUpdated Jun 5, 2026
andreadellacorte/groove
data-ai
VerifiedTrustedCommunity
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
5SKILL.mdUpdated Apr 24, 2026
andreadellacorte/groove-work-compound
documentation
VerifiedTrustedCommunity
Document lessons, update rules/templates/docs. Use to capture learnings after review.
5SKILL.mdUpdated Apr 24, 2026
andreadellacorte/groove-utilities-prime
tools
VerifiedTrustedCommunity
Load groove workflow context into the conversation. Run at the start of every session.
5SKILL.mdUpdated Apr 24, 2026