Skip to main content
skill CX Codex

groove-daily-start — Claude Code skill: start your workday

Prepares the workday: reviews recent days, creates today's memory file, loads tasks and lays out the agenda.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add andreadellacorte/groove --skill groove-daily-start -a claude-code
Open on GitHub

What groove-daily-start does

The skill runs at the start of the day and walks through a fixed sequence. It reads .groove/index.md for tasks.backend and memory.review_days, then looks at the last business days under .groove/memory/daily/. For each date it flags whether a start and an end section exist, and pulls commit activity from git log for that window.

Next it creates .groove/memory/daily/YYYY-MM-DD.md from the template at skills/groove-daily-start/templates/daily-start.md. If the file is already there, the step is skipped. Task state comes from /groove-utilities-task-analyse, open promises from /groove-utilities-memory-promises --list, open incidents from /groove-utilities-memory-mistakes --list. Tasks are not modified during start, only displayed.

If .groove/hooks/start.md has an ## Actions section, the skill runs each item in order and reports back per item. Missing or incomplete memory files do not block the start; the skill just reports them. One thing to know: without a .groove/ directory holding your config, the skill has no memory path and no review window to work from, so set that up first.

What it helps with

  • rebuild context from yesterday before picking up new work
  • create a daily memory file from a template
  • pull tasks from the backend and group them by status
  • spot days that never got an end-of-day entry
  • check open promises and incidents before starting

Example prompts for the agent

  • Start my workday: review recent days and create today's memory file
  • Run groove-daily-start and show me the agenda
  • Load my tasks and check open promises with groove-daily-start

How to install groove-daily-start

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-daily-start -a claude-code

2Manually: put the files in place

~/.claude/skills/groove-daily-start/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/groove-daily-start/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about groove-daily-start

How do I install groove-daily-start in Claude?

Run npx skills add andreadellacorte/groove --skill groove-daily-start -a claude-code. The skill lands at ~/.claude/skills/groove-daily-start/SKILL.md.

What does groove-daily-start do?

It reviews recent business days in .groove/memory/daily/, creates today's file, loads tasks and presents the agenda. Tasks stay untouched.

What does the skill need to work?

A .groove/ directory with an index.md that sets tasks.backend and memory.review_days. Without those it has no task source and no review window.

Source text

SKILL.md · MIT
---
name: groove-daily-start
description: "Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day."
license: MIT
allowed-tools: Bash(git:*) Read Write Edit AskUserQuestion
metadata:
  author: andreadellacorte
---

# groove-daily-start

## Outcome

The workday is prepared: recent days are reviewed, today's daily memory file is created, tasks are consolidated and presented, and the user knows what to work on.

## Acceptance Criteria

- Yesterday's daily memory file is reviewed (summary shown; warn if missing or no end section)
- Today's daily memory file is created with a start-of-day structure (if it does not already exist)
- Task list is loaded and presented (grouped by status)
- User has a clear picture of the day's agenda before starting work

## Constraints

- Read `.groove/index.md` for `tasks.backend` and `memory.review_days` config
- Memory path is always `.groove/memory/`
- Call `/groove-utilities-task-analyse` to get current task state
- **Review recent days:** If `.groove/memory/daily/` is empty (no files exist), skip this step entirely and note "Fresh install — no prior logs." Otherwise, identify the last `memory.review_days` business days (Mon–Fri) counting back from yesterday (skip Saturday and Sunday). For each date:
  - Check `.groove/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
    - `✗ YYYY-MM-DD — missing` if file does not exist
    - Show a one-line context from the file if present (e.g. first bullet from "Done today" or plan intent)
  - Show git activity: run `git log --oneline --after="YYYY-MM-DD 00:00" --before="YYYY-MM-DD 23:59:59"` — display commit count and first few titles; skip silently if not in a git repo or no commits
  - Do NOT block start if files are missing or incomplete — just report
- **Create new day memory:** Create today's file at `.groove/memory/daily/YYYY-MM-DD.md` using the template at `skills/groove-daily-start/templates/daily-start.md`. If the file already exists, skip (idempotent). Create `.groove/memory/daily/` if missing.
- After the recent-days review, check for open promises via `/groove-utilities-memory-promises --list`:
  - If open promises: show inline note: `→ N open promise(s) — run /groove-utilities-memory-promises --list to review`
  - If none: skip silently
- After the recent-days review, check for open mistake incidents via `/groove-utilities-memory-mistakes --list`:
  - If open incidents: show inline warning: `⚠ N open incident(s) — resolve at next /groove-work-compound`
  - If none: skip silently
- Do NOT modify tasks during start
- Present task list in a scannable format before the user begins
- After all standard steps: check if `.groove/hooks/start.md` exists
  - If it exists: read the `## Actions` section and execute each item in order; report completion per item
  - If it does not exist: skip silently

© andreadellacorte · MIT · andreadellacorte/groove

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set13

groove-utilities-task-analyse Pulls tasks from your project backend and groups them by status, so you have something to write into daily memory. CX Codex +1 588installs groove-utilities-memory-log-daily Writes the end-of-day entry to .groove/memory/daily/YYYY-MM-DD.md: what got done, which commits landed, what carries over. CX Codex +1 581installs groove-utilities-task-list Pulls active tasks from your configured backend and shows what is in progress, ready or blocked. Handy as a daily starting view. CX Codex +1 577installs groove-work-plan Researches your codebase and writes a concrete implementation plan with ordered steps, file paths and function names. Meant to run after brainstorming. CX Codex +1 544installs groove-work-compound This skill documents lessons after a review or planning session, updates project rules and templates, and traces root causes of mistakes. CX Codex +1 540installs groove-work-exec This skill takes a finished implementation plan and writes the code, tests and docs for it, logging progress in your task backend. Use it once planning is done. CX Codex +1 536installs groove-admin-update Pulls the latest groove skills and applies pending migrations to your local groove state. Useful when a new release lands but your config and memory are still on the old one. CX Codex +1 528installs groove-admin-cursor-hooks Registers groove's native Cursor hooks in .cursor/hooks.json: context re-priming after compaction, end-of-day reminders, a git commit buffer and managed-path protection. CX Codex +1 518installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor