Skip to main content
affpapa.org
RU EN
skill CX Codex

groove-work-plan — Claude Code skill: research code, write a plan

Researches your codebase and writes a concrete implementation plan with ordered steps, file paths and function names. Meant to run after brainstorming.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add andreadellacorte/groove --skill groove-work-plan -a claude-code
Open on GitHub

What groove-work-plan does

The skill goes through the repository looking for real patterns and constraints, then turns what it finds into a plan: ordered steps, file paths, function names, edge cases with their handling. Steps point at code that actually exists rather than guesses.

It works in a fixed order. First it reads tasks.backend from .groove/index.md, then hands codebase research to the Explore agent, then writes the plan. Doc output uses the template at skills/groove-work-plan/templates/plan-doc.md. If no prior brainstorm exists, it warns you and asks to confirm scope before continuing — worth running brainstorming first, otherwise the plan may cover the wrong ground.

No code gets written while planning. When tasks != none, a stage task titled YYYY-MM-DD, Plan is created through /groove-utilities-task-create. Tool access is limited to reading, writing, editing, file search and git, so nothing lands in a commit by accident.

What it helps with

  • map a codebase before a large change
  • lock down the order of implementation steps
  • surface existing patterns and constraints
  • spell out edge cases and how to handle them
  • create a stage task for the plan

Example prompts for the agent

  • research the code and write an implementation plan for this feature
  • draft a step-by-step plan with file paths and function names
  • run groove-work-plan on this task

How to install groove-work-plan

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-work-plan -a claude-code

2Manually: put the files in place

~/.claude/skills/groove-work-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/groove-work-plan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about groove-work-plan

How do I install groove-work-plan in Claude?

Run npx skills add andreadellacorte/groove --skill groove-work-plan -a claude-code. The skill then lives at ~/.claude/skills/groove-work-plan/SKILL.md.

What does groove-work-plan do?

It researches the codebase for patterns and constraints, then writes a concrete plan with ordered steps, file paths, function names and edge-case handling. It does not write code.

What does the skill need to run?

A .groove/index.md file with tasks.backend set, since that is where the task backend comes from. If no brainstorm happened earlier, the skill warns you and asks you to confirm scope.

Source text

SKILL.md · MIT 
---
name: groove-work-plan
description: "Research codebase, write concrete implementation plan. Use after brainstorming."
license: MIT
allowed-tools: Read Write Edit Glob Grep Bash(git:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

# 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`)

© andreadellacorte · MIT · andreadellacorte/groove

Similar skills

All skills for Agent setup: memory, context, orchestration →
update-implementation-plan official github Updates an existing implementation plan for new requirements, refactoring, package upgrades, or architecture changes. Use it when a plan needs actionable tasks and checks. 11,107installs create-implementation-plan official github This skill creates a Markdown implementation plan for features, refactoring, package upgrades, or infrastructure work. Use it when an agent needs an explicit task breakdown. 12,558installs ce-plan EveryInc Builds structured technical implementation plans without touching production code. Useful when scoping features before passing work to execution agents. CX Codex +1 3,700installs ralph-plan mastra-ai An interactive planning skill for Claude Code and coding agents. It helps build structured ralph-loop commands through guided dialog and codebase exploration. CX Codex +1 2,600installs speckit-plan github-spec-kit Executes implementation planning workflows inside spec-kit projects to produce research notes and interface contracts. CX Codex +1 2,500installs alan-plan tryalan-ai Walks the agent through planning: analyze the task, ask clarifying questions, draft the plan and persist it as an Alan artifact. CX Codex +1 1,800installs

From the same set13

groove-utilities-task-analyse Pulls tasks from your project backend and groups them by status, so you have something to write into daily memory. CX Codex +1 588installs groove-utilities-memory-log-daily Writes the end-of-day entry to .groove/memory/daily/YYYY-MM-DD.md: what got done, which commits landed, what carries over. CX Codex +1 581installs groove-utilities-task-list Pulls active tasks from your configured backend and shows what is in progress, ready or blocked. Handy as a daily starting view. CX Codex +1 577installs groove-daily-start Prepares the workday: reviews recent days, creates today's memory file, loads tasks and lays out the agenda. CX Codex +1 571installs groove-work-compound This skill documents lessons after a review or planning session, updates project rules and templates, and traces root causes of mistakes. CX Codex +1 540installs groove-work-exec This skill takes a finished implementation plan and writes the code, tests and docs for it, logging progress in your task backend. Use it once planning is done. CX Codex +1 536installs groove-admin-update Pulls the latest groove skills and applies pending migrations to your local groove state. Useful when a new release lands but your config and memory are still on the old one. CX Codex +1 528installs groove-admin-cursor-hooks Registers groove's native Cursor hooks in .cursor/hooks.json: context re-priming after compaction, end-of-day reminders, a git commit buffer and managed-path protection. CX Codex +1 518installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor