task
task
Backend-agnostic task management skill for groove. Reads backend config from .groove/index.md and routes all commands to the appropriate CLI or API.
Git Root Detection
Before running any command, detect the git root:
git rev-parse --show-toplevel
All file paths (.groove/index.md, .beans.yml) are relative to git root.
Commands
| Command | Description |
|---|---|
list |
Show active, ready tasks from configured backend |
create |
Create task with title, type, parent, status |
update |
Update task status, body, or metadata |
archive |
Archive all completed/scrapped tasks (user confirms) |
analyse |
Summarise tasks by status for daily end/daily memory |
install |
Install configured task backend |
config |
Show or update task backend configuration |
$ARGUMENTS Routing
| $ARGUMENTS | Action |
|---|---|
help |
→ commands/help.md |
doctor |
→ commands/doctor.md |
list |
→ commands/list.md |
create |
→ commands/create.md |
update |
→ commands/update.md |
archive |
→ commands/archive.md |
analyse |
→ commands/analyse.md |
install |
→ commands/install.md |
config |
→ commands/config.md |
| (empty) | → commands/help.md |
Bootstrap
If .groove/index.md does not exist at git root, create it from skills/groove/templates/index.md before proceeding. Ask user to confirm the defaults or provide overrides.
File Structure
.groove/
└── index.md # shared groove config (frontmatter: tasks, memory, git.*)
.beans.yml # beans CLI config (at git root, owned by beans)
skills/task/
├── SKILL.md
├── commands/
│ ├── list.md
│ ├── create.md
│ ├── update.md
│ ├── archive.md
│ ├── analyse.md
│ ├── install.md
│ └── config.md
├── references/
│ └── backends.md
└── templates/
└── beans-config.md
More from andreadellacorte/groove
pdf-to-markdown
[Document Processing] Convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR). Cross-platform.
254agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
251groove
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
248find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
245groove-utilities-memory-log-daily
Write the daily memory log entry. Use at end of day to record what happened.
235groove-daily-start
Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.
231