andreadellacorte/groove-work-exec
skills/groove-work-exec/SKILL.md
Execute the implementation plan, track progress in the task backend. Use after planning.
$ install --global
skillsauthnpx skillsauth add andreadellacorte/groove groove-work-execInstall 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-work-exec
- description:
- Execute the implementation plan, track progress in the task backend. Use after planning.
- license:
- MIT
- allowed-tools:
- Read Write Edit Glob Grep Bash(git:*) AskUserQuestion
- author:
- andreadellacorte
groove-work-exec
Outcome
Code, tests, and artifacts are written per the plan. The work task is created/updated in the backend with progress notes. Output is ready for review.
Acceptance Criteria
- Implementation matches the plan from
/groove-work-plan - Work task body tracks progress with dated notes
- Output (code, tests, docs) is complete enough to hand off to
/groove-work-review - Stage task created/updated in backend:
YYYY-MM-DD, Work
Constraints
- Read
tasks.backendfrom.groove/index.mdto determine backend - If no prior plan exists, warn the user and ask them to confirm scope before proceeding
- Append progress notes to task body as work proceeds — do not overwrite
- Do not mark task as completed during this stage — that happens after review
- Create stage task via
/groove-utilities-task-createiftasks.backend != none(titleYYYY-MM-DD, Work)
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-task-install
development
VerifiedTrustedCommunity
Set up task backend and configuration.
5SKILL.mdUpdated Apr 24, 2026