andreadellacorte/groove

groove-work-exec

Execute the implementation plan, track progress in the task backend. Use after planning.

First seen Mar 4, 2026

Installation

$ npx skills add andreadellacorte/groove --skill groove-work-exec

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from andreadellacorte/groove · top by installs.

npx skills add andreadellacorte/groove

Browse all from andreadellacorte/groove

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Allowed toolsRead Write Edit Glob Grep Bash(git:*) AskUserQuestion
More metadata
author
andreadellacorte

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,155 B
  • docs SUMMARY.md 109 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 530 installs

SKILL.md

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)