groove-utilities-onboard Generate a GROOVE.md file at the project root — a concise onboarding guide for contributors joining a project that uses groove. Also optionally appends a groove section to CONTRIBUTING.md if it exists. Outcome New contributors understand how groove works in this project: which commands to run, where logs live, and what the compound loop expects of them. 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 (task backend, git strategy) Steps Read tasks.backend , memory.review_days , git.* from .groove/index.md ; memory is always .groove/memory/ , specs is always .groove/memory/specs/ Ask: "Any project-specific context to include? (e.g. which tasks to pick up, team conventions) — enter to skip" Write GROOVE.md from the template below, substituting live config values If CONTRIBUTING.md exists and does not already contain
: Append the following section:
Using groove This project uses groove for AI-assisted engineering workflow. See GROOVE.md for setup and commands.
Report: "GROOVE.md written" and whether CONTRIBUTING.md was updated GROOVE.md template
Groove Workflow This project uses groove — an AI-assisted engineering workflow companion.
Quick start
```bash
npx skills add andreadellacorte/groove
/groove-admin-install
Then start every session with:
/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
Key
Value
Task backend