SkillsAdd

andreadellacorte/groove

groove-work-plan

Research codebase, write concrete implementation plan. Use after brainstorming.

First seen Mar 3, 2026

Installation

$ npx skills add andreadellacorte/groove --skill groove-work-plan
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from andreadellacorte/groove · top by installs.

npx skills add andreadellacorte/groove
groove 625 groove-utilities-task-analyse 582 groove-admin-install 579 groove-utilities-memory-install 578 groove-utilities-task-install 575 groove-admin-config 574 groove-utilities-memory-log-daily 573 groove-utilities-task-list 571 groove-admin-doctor 565 groove-daily-start 565

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,271 B
  • docs SUMMARY.md 100 B

History

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

SKILL.md

groove-work-plan

Outcome

The codebase is researched for relevant patterns and constraints. A concrete implementation plan is written with ordered steps, file paths, and function names. Plan is captured as a task or doc.

Acceptance Criteria

  • Plan references actual code patterns found in the codebase (not assumptions)
  • Steps are ordered and specific enough to execute without ambiguity
  • File paths and function names are named where known
  • Edge cases are identified and handling is specified
  • Stage task created in backend: YYYY-MM-DD, Plan

Constraints

  • Read tasks.backend from .groove/index.md to determine backend
  • Use Explore agent for codebase research before writing the plan
  • Use template at skills/groove-work-plan/templates/plan-doc.md for doc output
  • Warn if no prior brainstorm exists — ask user to confirm scope before proceeding
  • Do not write code during plan — plan only
  • Create stage task via /groove-utilities-task-create if tasks != none (title YYYY-MM-DD, Plan)