chore: release v0.9.2 — daily start/end rename + daily start memory

Made-with: Cursor

Author: andreadellacorte

.groove/docs/sessions-vs-daily-and-work.md

@@ -6,11 +6,11 @@ Groove has three ways to scope “what I’m doing”:
 
 | Concept | Purpose |
 |--------|--------|
-| **Daily** | Time-bound bookends: startup (agenda, tasks) and closeout (memory, tasks, commit). |
+| **Daily** | Time-bound bookends: start (agenda, tasks) and end (memory, tasks, commit). |
 | **Tasks** | What to do — list, create, update, archive. |
 | **Sessions** | Named conversation context with start/resume/end and a session file. |
 
-For a single workstream, **daily + tasks + work** is enough: you start the day, work through tasks with the compound loop (brainstorm → plan → work → review → compound), and close out. Sessions add an extra layer (named context, session file) that overlaps with “today’s tasks” and closeout.
+For a single workstream, **daily + tasks + work** is enough: you start the day, work through tasks with the compound loop (brainstorm → plan → work → review → compound), and close out. Sessions add an extra layer (named context, session file) that overlaps with “today’s tasks” and end.
 
 So: **sessions are optional.** Use them only when you need multiple parallel contexts (e.g. two chats, two features) and want a named file per context. For most use, ignore session start/resume/end and rely on daily + tasks + work.
 

.groove/memory/specs/groove-vs-bonfire.md

@@ -57,8 +57,8 @@
 | Doc creation | `groove memory session doc <topic>` | `/bonfire doc <topic>` |
 | Review | Not present as standalone command | `/bonfire review` — blindspot detection, categorized by Fix Now / Needs Spec / Create Issues |
 | Config | `groove config` | `/bonfire config` |
-| Daily startup | `groove daily startup` | Not present |
-| Daily closeout | `groove daily closeout` | Not present |
+| Daily start | `groove daily start` | Not present |
+| Daily end | `groove daily end` | Not present |
 | Work stages | `groove work brainstorm/plan/work/review/compound` | Not present |
 | Task management | `groove task create/list/update/archive/analyse` | Not present |
 | Update/migrate | `groove update` | Not present |
@@ -177,14 +177,14 @@ Both tools have spec and doc creation — this is the most direct overlap.
 
 | Dimension | groove | bonfire |
 |---|---|---|
-| Daily startup | `groove daily startup` — load tasks, check yesterday's closeout, run hook | Not present |
-| Daily closeout | `groove daily closeout` — write memory logs, git commit per strategy, run hook | Not present |
+| Daily start | `groove daily start` — review yesterday, create today's daily memory, load tasks, run hook | Not present |
+| Daily end | `groove daily end` — write memory logs, git commit per strategy, run hook | Not present |
 | Work stages | 5 explicit stages: brainstorm → plan → work → review → compound | Implicit: start → work → end |
 | Stage tasks | Each stage creates a task in the configured backend | Not present |
 | Review | `groove work review` — evaluate output against plan, identify lessons | `/bonfire review` — blindspot detection on branch diff; Fix Now / Needs Spec / Create Issues |
 | Compound/learning | `groove work compound` — update project files, detect workflow learnings | Not present |
 | Workflow learnings | compound + session end prompt → `learned/<topic>.md` | Not present; mature knowledge graduates to CLAUDE.md |
-| Hooks | `.groove/hooks/startup.md` and `closeout.md` — custom user-defined actions | Not present |
+| Hooks | `.groove/hooks/start.md` and `end.md` — custom user-defined actions | Not present |
 
 ---
 
@@ -195,7 +195,7 @@ Both tools have spec and doc creation — this is the most direct overlap.
 1. **Compound engineering loop** — 5 explicit stages (brainstorm→plan→work→review→compound) with per-stage constraints; bonfire has no equivalent structured workflow
 2. **Multi-tier memory** — daily/weekly/monthly roll-up captures knowledge at different timescales; bonfire has a single living document
 3. **Task management** — beans/linear/github/none abstraction with full task lifecycle; bonfire has only an optional issues link
-4. **Daily rituals** — startup/closeout with hooks, task analysis, git commit; bonfire has no daily ceremony
+4. **Daily rituals** — start/end with hooks, task analysis, git commit; bonfire has no daily ceremony
 5. **Workflow learning accumulation** — `learned/<topic>.md` cold tier populated from compound + session end; bonfire has no dedicated long-term insight tier
 6. **Formal migration system** — ordered migration runner handles config evolution across any version gap; bonfire auto-detects key changes but has no runner
 7. **Per-component git strategy** — independent `git.memory`, `git.tasks`, `git.hooks`; bonfire has a single global strategy

.groove/memory/specs/groove-vs-groove.md

@@ -22,7 +22,7 @@ Synthesised from scope observations across all three comparisons:
 
 - **A lean, markdown-only engineering workflow companion** — no runtime, no Bun, no TypeScript; portable, lightweight, installs anywhere Claude Code runs
 - **Project-scoped, not global** — `.groove/` lives in the repo; PAI-style global installs (`~/.claude/`) are out of scope
-- **Opinionated daily rhythm** — the startup/closeout ceremony is a core differentiator; no other compared tool has it
+- **Opinionated daily rhythm** — the start/end ceremony is a core differentiator; no other compared tool has it
 - **Explicit 5-stage compound loop** — the most structured development workflow of any compared tool; "80% of value in plan and review" is baked in
 - **Predictable explicit invocation** — `/groove <skill> <command>` is more predictable than auto-discovery; keep it
 - **Backend-agnostic task abstraction** — beans/linear/github/none is unique; no other tool has an abstraction layer over task backends
@@ -36,7 +36,7 @@ Synthesised from scope observations across all three comparisons:
 | Ordered migration runner with dual versioning | night-market + PAI | Unique; enables safe config evolution across any version gap |
 | Per-component git strategy (memory/tasks/hooks) | night-market + PAI + bonfire | Unique; teams need different sharing strategies per component |
 | Explicit 5-stage compound loop | night-market + PAI + bonfire | Most opinionated and structured workflow; core value prop |
-| Structured daily rituals (startup/closeout) | night-market + PAI + bonfire | No other tool has an explicit daily ceremony |
+| Structured daily rituals (start/end) | night-market + PAI + bonfire | No other tool has an explicit daily ceremony |
 | Learned memory tier (`learned/<topic>.md`) | night-market + PAI | Unique long-term insight accumulation; no other tool has this cold tier |
 | Multi-tier memory roll-ups (daily→weekly→monthly) | night-market + PAI + bonfire | No other tool has this temporal pyramid |
 | Config wizard + interactive setup | night-market + PAI | Unique guided configuration; lowers barrier to entry |

.groove/memory/specs/groove-vs-night-market.md

@@ -92,7 +92,7 @@
 | Compound loop | Explicit 5 stages: brainstorm → plan → work → review → compound | attune: brainstorm → plan → work → review → execute (similar structure; lighter constraints) |
 | TDD enforcement | Not present | imbue: PreToolUse hook blocks file writes until tests exist — enforced, not advisory |
 | Code review | Not present as built-in | pensive: NASA Power of 10 safety patterns; tracks command usage frequency and failure rates |
-| Daily rituals | startup (task load, hook) + closeout (memory logs, git commit, hook) | `/catchup` reads recent git history at session start; no closeout ritual |
+| Daily rituals | start (task load, hook) + end (memory logs, git commit, hook) | `/catchup` reads recent git history at session start; no end ritual |
 | Spec creation | `memory session spec <topic>` → structured spec file at `sessions/specs/` | spec-kit plugin; `attune:project-init` scaffolds requirements |
 | Plan docs | Templated brainstorm + implementation plan with codebase research | spec-kit task breakdown into 2-5 minute resumable chunks |
 | Workflow learnings | `work compound` detects AI/process lessons → `.groove/memory/learned/<topic>.md` | pensive tracks failure rates and flags unstable workflows; no explicit capture ritual |
@@ -163,7 +163,7 @@ Things night-market does not have that groove should preserve and develop:
 2. **Git strategy per component** — fine-grained control over what gets committed (`git.memory/tasks/hooks`) is unique; useful for teams with different sharing conventions.
 3. **Explicit 5-stage compound loop** — more opinionated and constraint-enforcing than attune's lifecycle; the "80% of value in plan and review" insight is baked into the skill.
 4. **Learned memory tier** — `.groove/memory/learned/<topic>.md` as an explicit cold-tier for workflow insights with routing from both compound and session end; not present in night-market.
-5. **Daily rituals with structured log roll-ups** — startup/closeout with daily→weekly→monthly roll-up chain; no equivalent in night-market.
+5. **Daily rituals with structured log roll-ups** — start/end with daily→weekly→monthly roll-up chain; no equivalent in night-market.
 6. **Config wizard + version tracking** — `/groove config` wizard and `groove-version:` migration gating is more robust than night-market's version management.
 7. **groovebook (planned)** — a shared PR-based commons for cross-user workflow learnings; no equivalent exists.
 

.groove/memory/specs/groove-vs-pai.md

@@ -94,7 +94,7 @@
 |---|---|---|
 | Development loop | 5 stages: brainstorm → plan → work → review → compound | The Algorithm: 7 phases — observe → think → plan → build → execute → verify → learn |
 | Enforcement | Advisory — SKILL.md constraints interpreted by Claude | PreToolUse hooks enforce security checks; Algorithm phases tracked in PRD frontmatter |
-| Daily rituals | startup + closeout with memory logs, task analysis, git commit | Not present — SessionStart/SessionEnd hooks handle context loading/capture |
+| Daily rituals | start + end with memory logs, task analysis, git commit | Not present — SessionStart/SessionEnd hooks handle context loading/capture |
 | Spec creation | `memory session spec <topic>` → structured markdown spec | PRD format — YAML frontmatter with atomic criteria, decisions, verification evidence |
 | Task tracking | Backend-agnostic: beans / linear / github / none | Work registry at `MEMORY/WORK/`; PRD files are task units |
 | Workflow learnings | compound detects AI/process lessons → `learned/` | `WorkCompletionLearning` hook captures lessons automatically on every SessionEnd |
@@ -224,7 +224,7 @@ Things PAI does not have that groove should preserve:
 1. **Explicit migration system** — PAI's installer merges settings manually and avoids breaking changes; groove's ordered migration runner handles config evolution safely across any version gap.
 2. **Git strategy per component** — Fine-grained `git.memory/tasks/hooks` control; PAI has no equivalent.
 3. **Explicit 5-stage compound loop** — Brainstorm→plan→work→review→compound with per-stage constraints; PAI's Algorithm is similar (7 phases) but groove's stages are more opinionated about _when_ to run each.
-4. **Structured daily rituals** — Startup/closeout with daily→weekly→monthly roll-up chain; PAI has no equivalent scheduled closeout.
+4. **Structured daily rituals** — Start/end with daily→weekly→monthly roll-up chain; PAI has no equivalent scheduled end ritual.
 5. **Backend-agnostic task layer** — beans / linear / github / none abstraction; PAI ties task tracking to PRD files and WORK/ memory only.
 6. **Session spec/doc creation** — `memory session spec` and `memory session doc` produce structured artefacts scoped to the current session; PAI generates PRDs but not session-scoped specs.
 7. **groovebook (planned)** — PR-based shared learning commons; no equivalent exists in PAI.

.groove/memory/specs/night-market-vs-pai.md

@@ -102,7 +102,7 @@
 | Spec creation | spec-kit plugin; attune:project-init scaffolds requirements | PRD format — binary-testable ISC checkboxes |
 | TDD enforcement | imbue: PreToolUse blocks file writes until tests exist | Not present as a dedicated workflow feature |
 | Code review | pensive: NASA Power of 10 safety patterns; tracks failure rates per command | Not present as dedicated skill; security review via Fabric patterns |
-| Daily rituals | `/catchup` reads recent git history at session start | SessionStart hooks (LoadContext, KittyEnvPersist); no closeout ritual |
+| Daily rituals | `/catchup` reads recent git history at session start | SessionStart hooks (LoadContext, KittyEnvPersist); no end ritual |
 | Actions/pipelines | Not present | Atomic Actions + Pipelines + Flows on cron schedule (UNIX pipe model) |
 | Fabric patterns | Not present | 237 pre-built workflows (extraction, summarization, analysis, creation, security) |
 | Workflow learnings | pensive tracks stability metrics; no explicit user-facing capture ritual | `WorkCompletionLearning` hook captures lessons automatically on every SessionEnd |

CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to groove will be documented in this file.
 
+## [0.9.2] - 2026-03-02
+
+### Changed
+- Daily commands renamed: `startup` / `closeout` → `start` / `end`. Use `groove daily start` and `groove daily end`.
+- Hook files renamed: `.groove/hooks/startup.md` and `closeout.md` → `start.md` and `end.md`.
+
+### Added
+- **Daily start** now reviews yesterday's daily memory (shows summary; warns if missing or no end section) and creates today's daily memory file with a start-of-day structure.
+- **memory init daily** — creates today's `<memory>/daily/YYYY-MM-DD.md` with start-of-day template (Plan for today). Called from daily start; at daily end, `memory log daily` appends the closeout sections.
+
+### Migration
+- If you have custom `.groove/hooks/startup.md` or `closeout.md`, rename them to `start.md` and `end.md` so the new daily commands run them. No migration script; manual rename only.
+
 ## [0.9.1] - 2026-03-02
 
 ### Fixed
@@ -139,13 +152,13 @@ groove task install
 
 ### Added
 - Per-component git strategy: `git:` is now a mapping with `memory:`, `tasks:`, and `hooks:` sub-keys
-- Each sub-key independently controls what gets committed during daily closeout and what `.groove/.gitignore` ignores
+- Each sub-key independently controls what gets committed during daily end and what `.groove/.gitignore` ignores
 
 ### Changed
 - `.groove/.gitignore` is now generated from per-component strategies instead of a single flat value
 - `git.hooks` defaults to `commit-all` (hooks are team-shareable by default)
 - Beans task path changed from `.beans` to `.groove/tasks` — tasks now live inside the groove directory tree
-- Daily closeout commit logic updated to stage per-component based on each `git.*` value
+- Daily end commit logic updated to stage per-component based on each `git.*` value
 
 ### Removed
 - `finder:` config key — skill discovery uses `npx skills` / skills.sh directly; no config key needed
@@ -208,7 +221,7 @@ If you had bonfire installed, remove it: `npx skills remove bonfire`
 
 ### Added
 - User-defined daily hooks — `groove install` creates `.groove/hooks/` (with `.gitkeep`)
-- `daily startup` and `daily closeout` execute `.groove/hooks/startup.md` / `.groove/hooks/closeout.md` if present, skip silently if not
+- `daily start` and `daily end` execute `.groove/hooks/start.md` / `.groove/hooks/end.md` if present, skip silently if not
 - Hook templates at `skills/daily/templates/hooks/` document the format
 
 ## [0.3.1] - 2026-02-28
@@ -252,7 +265,7 @@ If you had bonfire installed, remove it: `npx skills remove bonfire`
 
 ### Added
 - Initial release
-- `daily` skill — startup and closeout rituals
+- `daily` skill — start and end rituals
 - `work` skill — compound engineering loop
 - `task` skill — backend-agnostic task management
 - `memory` skill — log population and session wrapper

README.md

@@ -20,7 +20,7 @@ groove install
 
 | Skill | Commands | Purpose |
 |---|---|---|
-| `daily` | `startup`, `closeout` | Bookend the workday |
+| `daily` | `start`, `end` | Bookend the workday |
 | `work` | `brainstorm`, `plan`, `work`, `review`, `compound` | Reduce rework through structured stages |
 | `task` | `list`, `create`, `update`, `archive`, `analyse` | Task tracking — configurable backend |
 | `memory` | `log daily/weekly/monthly/git`, `session start/resume/end/spec/doc/review` | Logs + session context |
@@ -38,8 +38,8 @@ Companions extend groove and are not listed in the core skills table above. Inst
 ## Usage
 
 ```
-/groove daily startup         — start the workday
-/groove daily closeout        — end the workday
+/groove daily start           — start the workday
+/groove daily end             — end the workday
 
 /groove work brainstorm       — clarify scope
 /groove work plan             — write implementation plan
@@ -53,7 +53,7 @@ Companions extend groove and are not listed in the core skills table above. Inst
 
 /groove memory session start  — start session
 /groove memory session resume — resume an existing session
-/groove memory log daily      — write daily closeout log
+/groove memory log daily      — write daily end log
 
 /groove doctor                — check all backends are healthy
 /groove update                — apply pending migrations

skills/daily/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: daily
-description: "Daily startup and closeout rituals. Use when: (1) starting the workday; (2) wrapping up the day. NOT for: mid-day task management (use task); compound loop (use work); memory directly (use memory)."
+description: "Daily start and end rituals. Use when: (1) starting the workday; (2) wrapping up the day. NOT for: mid-day task management (use task); compound loop (use work); memory directly (use memory)."
 license: MIT
 allowed-tools: Bash(git:*) Read Write Edit AskUserQuestion
 metadata:
@@ -28,16 +28,16 @@ All config reads use `.groove/index.md` at git root.
 
 | Command | Description |
 |---|---|
-| `startup` | Start the workday: verify yesterday's closeout, load tasks, prepare agenda |
-| `closeout` | End the workday: write memory, analyse tasks, commit if configured |
+| `start` | Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda |
+| `end` | End the workday: write memory, analyse tasks, commit if configured |
 
 ## $ARGUMENTS Routing
 
 | $ARGUMENTS | Action |
 |---|---|
 | `help` | → `commands/help.md` |
-| `startup` | → `commands/startup.md` |
-| `closeout` | → `commands/closeout.md` |
+| `start` | → `commands/start.md` |
+| `end` | → `commands/end.md` |
 | _(empty)_ | → `commands/help.md` |
 
 ## Bootstrap