groove

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

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.

Set up task backend and configuration.

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.

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.

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

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

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

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

Display all groove skills and commands with live config values.

Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.

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

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

Set up memory backend and configuration.

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

Check task backend health and connectivity.

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

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

Check memory backend health and configuration.

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

Record git activity summary in memory log.

Roll up the monthly memory log from weekly entries.

Roll up the weekly memory log from daily entries.

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.

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

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

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

Analyse task status and distribution across the configured backend.

Archive a completed task in the configured backend.

Configure task backend settings interactively.

Create a new task in the configured backend.

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

Update an existing task in the configured backend.

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

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

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

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

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

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

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