andreadellacorte

Groove engineering workflow system. Top-level entry point. Use groove-daily-, groove-work-, groove-utilities-, groove-admin- for all workflow and admin commands.

Analyse task status and distribution across the configured backend.

Install groove backends, companions, and AGENTS.md bootstrap. Run once per repo.

Set up memory backend and configuration.

Write the daily memory log entry. Use at end of day to record what happened.

Set up task backend and configuration.

Create or update .groove/index.md config interactively. Run before groove install.

List active tasks in the configured backend. Use to see current task status.

Run all groove health checks: config, backends, companions, AGENTS.md.

Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.

End the workday: write memory, analyse tasks, run end hook. Use when wrapping up the day.

Check memory backend health and configuration.

Check task backend health and connectivity.

Clarify scope through dialogue, surface key decisions and open questions. Use before planning.

Update an existing task in the configured backend.

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

Evaluate output, identify lessons, decide accept/rework. Use after implementation.

Roll up the weekly memory log from daily entries.

Display all groove skills and commands with live config values.

Create outcome spec (overview, decisions, steps, edge cases). Use $ARGUMENTS as spec topic if provided.

Create a new task in the configured backend.

Review current branch for blindspots; fix now / needs spec / create issues.

Document lessons, update rules/templates/docs. Use to capture learnings after review.

Load groove workflow context into the conversation. Run at the start of every session.

Record git activity summary in memory log.

Check if a newer version of groove is available on GitHub.

Roll up the monthly memory log from weekly entries.

Execute the implementation plan, track progress in the task backend. Use after planning.

Configure task backend settings interactively.

Archive a completed task in the configured backend.

Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.

Log a workflow mistake, fix its root cause, and graduate the lesson to learned memory. Use when the agent makes an error you want to prevent recurring.

Pull latest groove skills and apply pending migrations to local groove state.

Install groove's Cursor native hooks into .cursor/hooks.json. Enables compaction-safe re-priming, session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.

Capture and resolve deferred items from a session ('we'll come back to that'). Use $ARGUMENTS as the promise text, or --list / --resolve N.

Create a 'how does X work' documentation file for a codebase component or concept. Use $ARGUMENTS as the doc topic if provided.

Analyse workflow trends: session ratings, recurring mistakes, and learnings over a period. Use for weekly or monthly reflection.

Graduate a workflow insight from learned/ .md into AGENTS.md as a permanent constraint. Use when a lesson is stable enough to apply to every future session.

Browse and review open learning PRs in the configured groovebook repo. Use to participate in the shared groove commons.

Publish a workflow learning to the groovebook shared commons as a GitHub PR. Use after groove-work-compound when a learning is worth sharing.

Generate a GROOVE.md onboarding guide for contributors to a groove-enabled project. Explains the compound loop, commands, and conventions.

Install a rich Claude Code statusline into /.claude/hooks/ and /.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.