# Groove Workflow Context

groove is installed in this repo. Use `/groove-*` skills for all workflow commands.

## Config
tasks:      <tasks value>
memory:     <memory value>
git.memory: <git.memory value>
git.tasks:  <git.tasks value>
git.hooks:  <git.hooks value>

## Key commands
/groove-daily-start           — start the workday
/groove-daily-end             — end the workday
/groove-work-brainstorm       — clarify scope (YAGNI enforced)
/groove-work-plan             — research codebase, write implementation plan
/groove-work-exec             — execute the plan
/groove-work-review           — evaluate output, decide accept/rework
/groove-work-compound         — document lessons into existing project files
/groove-utilities-task-list   — show active, ready tasks
/groove-utilities-task-create — create a task
/groove-utilities-task-analyse — summarise tasks by status
/groove-utilities-memory-log-daily — write daily end log

## Conventions
- Stage tasks: "YYYY-MM-DD, <Stage>" (no numbers; e.g. 2026-02-28, Brainstorm; 2026-02-28, Compound — topic)
- Memory logs: <memory value>daily/, weekly/, monthly/, git/
- Task completion requires "Summary of Changes" in body before marking done
- Archive is always user-triggered — never automatic during end
- 80% of compound loop value is in plan and review — do not skip them

## Constraints
- Do not edit files under `skills/` or `.agents/skills/` — managed by groove update, changes will be overwritten
- User zone: `.groove/` is yours — config, hooks, memory, and learned insights are all safe to edit