Groove Work Exec

This is the execution stage of the Groove workflow. It picks up after you've run the planning skill, writes the actual code and tests according to that plan, and logs progress to your task backend as dated notes. The skill checks your `.groove/index.md` for the backend config and creates a work stage task automatically. What I like here is the constraint that explicitly tells Claude not to mark tasks complete during execution, that happens in the review stage. If you try to run this without a plan first, it warns you and asks for confirmation. It's opinionated about the workflow sequence, which is exactly what you want from a process skill.

skills.sh installs: 536
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-work-exec --agent claude-code

Installs into .claude/skills of the current project.

Files

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.backend from .groove/index.md to 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-create if tasks.backend != none (title YYYY-MM-DD, Work)