mcpField
G
groove-work-plan

groove-work-plan

github.com/andreadellacorteDevelopment6544 installsUpdated 14w ago
Repository

About groove-work-plan

A skill for researching a codebase and producing an ordered, executable implementation plan without writing code. It is intended for planning work grounded in existing patterns, with scope confirmation when no prior brainstorm exists.

Key features

  1. 01Research code patterns and constraints
  2. 02Write ordered implementation steps
  3. 03Name relevant files and functions
  4. 04Identify edge cases and handling
  5. 05Create a stage planning task

Use cases

  1. 01Plan a feature using existing code patterns
  2. 02Document implementation steps before coding
  3. 03Clarify scope when no brainstorm exists

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/andreadellacorte/groove --skill groove-work-plan

After installing, type/groove-work-planin Claude Code to confirm it loaded.

Bundled filestemplates/plan-doc.md

Details

From the project README

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)

Comments

Markdown supported