v0.11.3 — faster install and fresh-start UX

- groove-admin-install calls groove-admin-config --defaults on first run
- groove-admin-config supports --defaults flag (no prompts)
- groove-utilities-task-install uses beans init + prefix update instead of manual scaffold
- groove-daily-start skips recent-days review on fresh install

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: andreadellacorte-converge

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to groove will be documented in this file.
 
+## [0.11.3] - 2026-03-06
+
+### Changed
+- `groove-admin-install`: calls `groove-admin-config --defaults` on first run — no config prompts during install.
+- `groove-admin-config`: `--defaults` flag applies all defaults without prompting; key=value args now use defaults for unspecified keys.
+- `groove-utilities-task-install`: beans backend now initialised with `beans init` instead of manual template scaffolding; prefix derived from repo name and written back to the generated `.beans.yml`.
+- `groove-daily-start`: skips recent-days review when `<memory>/daily/` is empty (fresh install).
+
 ## [0.11.2] - 2026-03-06
 
 ### Changed

skills/groove-admin-config/SKILL.md

@@ -24,7 +24,9 @@ metadata:
 
 ## Steps
 
-Walk the user through each config key in order. For each key: show the current value (or default if new), explain what it does, and ask to confirm or change.
+If `--defaults` is passed: skip all prompts, apply all defaults, and proceed directly to writing the config (step 1 of "After all keys are confirmed"). Report the defaults being applied.
+
+Otherwise, walk the user through each config key in order. For each key: show the current value (or default if new), explain what it does, and ask to confirm or change.
 
 ### Keys and defaults
 
@@ -46,7 +48,8 @@ After all keys are confirmed:
 ## Constraints
 
 - If `.groove/index.md` already exists, pre-fill each question with the current value
-- If run non-interactively (arguments provided), apply them without prompting: e.g. `groove-admin-config tasks=linear git.memory=hybrid`
+- If `--defaults` is passed, apply all defaults without any prompting — used by `groove-admin-install` for zero-friction first-time setup
+- If other arguments are provided (e.g. `tasks=linear git.memory=hybrid`), apply them without prompting and use defaults for any unspecified keys
 - Always write `groove-version:` matching the installed version from `skills/groove/SKILL.md`
 
 ### Git strategy → `.groove/.gitignore`

skills/groove-admin-install/SKILL.md

@@ -27,7 +27,7 @@ All groove backends are installed in dependency order, groove-wide companion ski
 
 Run in order:
 
-1. If `.groove/index.md` does not exist, run `/groove-admin-config` to create it
+1. If `.groove/index.md` does not exist, run `/groove-admin-config --defaults` to create it with all defaults (no prompts)
 2. Run `/groove-utilities-task-install` — installs the configured task backend (e.g. beans)
 3. Run `/groove-utilities-memory-install` — creates memory directories
 4. Install companion skills:

skills/groove-daily-start/SKILL.md

@@ -24,7 +24,7 @@ The workday is prepared: recent days are reviewed, today's daily memory file is
 
 - Read `.groove/index.md` for `tasks:`, `memory:`, and `recent_memory_days:` config
 - Call `/groove-utilities-task-analyse` to get current task state
-- **Review recent days:** Identify the last `recent_memory_days` business days (Mon–Fri) counting back from yesterday (skip Saturday and Sunday). For each date:
+- **Review recent days:** If `<memory>/daily/` is empty (no files exist), skip this step entirely and note "Fresh install — no prior logs." Otherwise, identify the last `recent_memory_days` business days (Mon–Fri) counting back from yesterday (skip Saturday and Sunday). For each date:
   - Check `<memory>/daily/YYYY-MM-DD.md`:
     - `✓ YYYY-MM-DD — start + end logged` if both start-of-day and end sections exist
     - `~ YYYY-MM-DD — start only, no end logged` if only start section present

skills/groove-utilities-task-install/SKILL.md

@@ -31,10 +31,10 @@ The configured task backend is installed and verified reachable. User is informe
 - After install, run a simple reachability check (e.g., `beans version` or `gh auth status`)
 - If CLI is already installed, report current version and skip install
 - If `tasks: beans` and `.beans.yml` does not exist at git root:
-  - Derive `[PROJECT_PREFIX]` from the git repo name (last path component of `git remote get-url origin`, uppercased, non-alphanumeric stripped) — e.g. `groove` → `GRV`
-  - Scaffold `.beans.yml` from `skills/groove-utilities-task-install/templates/beans-config.md` with the derived prefix
-  - Create `.groove/tasks/` directory if it does not exist
-  - Report the path written
+  - Run `beans init` to initialise the task store and generate `.beans.yml` with beans defaults
+  - Derive `[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 remote
+  - Update the `prefix:` field in the generated `.beans.yml` to the derived prefix (e.g. `GRV-`)
+  - Report the path written and the prefix used
 - If `tasks: beans`: write a minimal stub to `AGENTS.md` at git root:
   - Wrap in `<!-- groove:task:start -->` / `<!-- groove:task:end -->` fenced section
   - Stub content:

skills/groove/SKILL.md

@@ -5,7 +5,7 @@ license: MIT
 allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) Bash(mkdir:*) AskUserQuestion
 metadata:
   author: andreadellacorte
-  version: "0.11.2"
+  version: "0.11.3"
 ---
 
 <!-- groove:managed — do not edit; changes will be overwritten by groove update -->