groove-utilities-onboard

GROOVE.md

CONTRIBUTING.md

Outcome

Acceptance Criteria

• GROOVE.md

  exists at the project root with project-specific config values substituted
• If

  CONTRIBUTING.md

  exists, it contains a "## Using groove" section linking to

  GROOVE.md

• Content reflects actual configured values (memory path, task backend, specs path)

Steps

1. Read

   tasks:

   ,

   memory:

   ,

   specs:

   ,

   git.*

   from

   .groove/index.md

2. Ask: "Any project-specific context to include? (e.g. which tasks to pick up, team conventions) — enter to skip"
3. Write

   GROOVE.md

   from the template below, substituting live config values
4. If

   CONTRIBUTING.md

   exists and does not already contain

   <!-- groove:onboard -->

   :
   • Append the following section:
     markdown

     <!-- groove:onboard -->
     ## Using groove
     This project uses [groove](https://github.com/andreadellacorte/groove) for AI-assisted engineering workflow. See [GROOVE.md](./GROOVE.md) for setup and commands.
     <!-- groove:onboard:end -->

5. Report: "GROOVE.md written" and whether CONTRIBUTING.md was updated

GROOVE.md template

# Groove Workflow

This project uses [groove](https://github.com/andreadellacorte/groove) — an AI-assisted engineering workflow companion.

## Quick start

```bash
npx skills add andreadellacorte/groove
/groove-admin-install

/groove-utilities-prime

Daily workflow

/groove-daily-start     — review yesterday, load tasks, set agenda
/groove-daily-end       — write memory, commit logs

Compound loop (for any feature or fix)

/groove-work-brainstorm — clarify scope
/groove-work-plan       — research and plan
/groove-work-exec       — implement
/groove-work-review     — evaluate output
/groove-work-compound   — capture lessons

Config

<tasks>

<memory>

<specs or (default: <memory>/specs/)>

<git.memory>

Conventions

• Stage tasks are named

  YYYY-MM-DD, <Stage>

  — no numbers
• Task completion requires a "Summary of Changes" in the task body before marking done
• Archive is always user-triggered — never automatic

Where things live

• Config:

  .groove/index.md

• Daily logs:

  <memory>daily/

• Learned insights:

  <memory>learned/

• Specs:

  <specs or (default: <memory>/specs/)>

• Hooks:

  .groove/hooks/

  (start.md, end.md)

Constraints

• Read

  .groove/index.md

  and substitute all

  <placeholder>

  values before writing
• If

  GROOVE.md

  already exists: ask "GROOVE.md exists — overwrite, update, or skip?" before touching it
• The

  <custom-context>

  block is replaced with user-provided context or removed if none
• Do not create

  CONTRIBUTING.md

  if it doesn't exist — only append to existing files

• GROOVE.md

  should be short enough to read in 2 minutes