Back to Details

groove-utilities-prime

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- groove:managed — do not edit; changes will be overwritten by groove update -->
<!-- groove:托管内容 — 请勿编辑；修改内容会在groove更新时被覆盖 -->

groove-utilities-prime

groove-utilities-prime

Outcome

预期效果

The agent receives full groove workflow context in the conversation — config, key commands, conventions, and constraints. Run at the start of every session before doing any work.
Agent会在对话中获取完整的groove工作流上下文，包括配置、关键命令、约定和约束。请在每个会话开始、开展任何工作之前运行。

Acceptance Criteria

验收标准

  • Agent is shown current config values from 
    .groove/index.md
  • Agent is shown all key commands, conventions, and constraints
  • If a newer version of groove is available, agent is notified
  • 向Agent展示
    .groove/index.md
    中的当前配置值
  • 向Agent展示所有关键命令、约定和约束
  • 如果有可用的groove新版本，需通知Agent

Output format

输出格式

Output the following to the conversation (do not write to any file):
undefined
将以下内容输出到对话中（请勿写入任何文件）：
undefined

Groove Workflow Context

Groove Workflow Context

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

Config

Config

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

Key commands

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
/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

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
  • 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

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
undefined
  • 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
undefined

Version check

版本检查

Before outputting context, check if 
.groove/.cache/last-version-check
does not contain today's date:
  1. Read 
    .groove/.cache/last-version-check
    — if absent or not today's date, proceed
  2. Fetch latest release from 
    https://api.github.com/repos/andreadellacorte/groove/releases/latest
  3. If a newer version exists, prepend to the output: 
    ⚠ New version of groove available: v<latest> — run: /groove-admin-update
  4. Write today's date to 
    .groove/.cache/last-version-check
  5. If the API call fails, skip silently — do not block prime
在输出上下文之前，请检查
.groove/.cache/last-version-check
是否未包含今日日期：
  1. 读取
    .groove/.cache/last-version-check
    ——如果文件不存在或日期不是今日，继续执行
  2. 从
    https://api.github.com/repos/andreadellacorte/groove/releases/latest
    获取最新发布版本
  3. 如果存在更新版本，在输出内容开头添加如下内容： 
    ⚠ New version of groove available: v<latest> — run: /groove-admin-update
  4. 将今日日期写入
    .groove/.cache/last-version-check
  5. 如果API调用失败，静默跳过——不要阻塞prime运行

Constraints

约束

  • Read 
    .groove/index.md
    frontmatter to substitute 
    tasks:
    , 
    memory:
    , and 
    git.*
    placeholders
  • Output to conversation only — do not write to AGENTS.md or any other file (except updating 
    .groove/.cache/last-version-check
    )
  • Version check runs at most once per day — gate on 
    .groove/.cache/last-version-check
    date
  • 读取
    .groove/index.md
    前置元数据来替换
    tasks:
    、
    memory:
    和
    git.*
    占位符
  • 仅输出到对话中——请勿写入AGENTS.md或其他任何文件（更新
    .groove/.cache/last-version-check
    除外）
  • 版本检查每天最多运行一次——通过
    .groove/.cache/last-version-check
    的日期进行管控