with one click
groove-utilities-task-install
Set up task backend and configuration.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Set up task backend and configuration.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
| name | groove-utilities-task-install |
| description | Set up task backend and configuration. |
| license | MIT |
| allowed-tools | Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) AskUserQuestion |
| metadata | {"author":"andreadellacorte"} |
The configured task backend is installed and verified reachable. User is informed of what was installed and how to use it.
tasks.storage: nonetasks.storage from .groove/index.md to determine backend (if the key is still named tasks.backend from an older config, treat it as the storage value). If the key is missing or invalid, you may pause and use AskUserQuestion so the user can choose a backend (beans, linear, github, or none); then ensure .groove/index.md is updated accordingly (via /groove-admin-config or an equivalent edit) before continuing.tasks.storage: none, print friendly no-op message and exitbeans: hmans/beans — Installation sectionlinear: schpet/linear-cli — install section (third-party CLI; not Linear’s hosted docs)github: GitHub CLIbeans version, linear --version / linear --help, or gh version / gh auth status as appropriate)tasks.storage: beans and .beans.yml does not exist at git root:
beans init to initialise the task store and generate .beans.yml with beans defaults[PROJECT_PREFIX] from the git repo name (last path component of git remote get-url origin, stripped of .git, uppercased, non-alphanumeric stripped) — e.g. groove → GRV; fall back to the directory name if no remoteprefix: field in the generated .beans.yml to the derived prefix (e.g. GRV-)path: in .beans.yml to .groove/tasks so the task store lives under groove (aligned with git.tasks and .groove/.gitignore). Create .groove/tasks if it does not exist. If the default .beans directory was created and is non-empty, move its contents into .groove/tasks and remove the empty .beans directory.