# groove-utilities-task-create

Creates a task in the configured backend, fills its fields, and returns the task ID. Useful when an agent needs to record work in context.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 541 installs · ★ 6
- Author: andreadellacorte
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/andreadellacorte/groove/tree/HEAD/skills/groove-utilities-task-create/SKILL.md
- Updated: 2026-07-24
- HTML: https://affpapa.org/en/nevibecode/skills/groove-utilities-task-create

## What it does

The skill reads `tasks.backend` from `.groove/index.md` and uses that setting to choose how a task is created. When a title or type is missing, it asks for them. It can infer a parent from open tasks and recent work, then asks for confirmation when the relationship is unclear. New tasks use `in-progress` by default and are never marked complete during creation.

For non-trivial work, the task gets a structured body with Context, Goal, Acceptance Criteria, and Links. The supported paths cover `beans`, `linear`, and `github`, using their CLI, MCP, or task files as described by the backend. When `tasks.backend` is `none`, the skill performs no creation and gives a friendly message.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-task-create -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/groove-utilities-task-create/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/groove-utilities-task-create/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-task-create -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/groove-utilities-task-create/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-task-create -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/groove-utilities-task-create/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install andreadellacorte/groove groove-utilities-task-create
```

2. **Manually: put the files in place**
- File: `.github/skills/groove-utilities-task-create/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-task-create -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/andreadellacorte/groove --path skills/groove-utilities-task-create
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/groove-utilities-task-create/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add andreadellacorte/groove --skill groove-utilities-task-create -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/andreadellacorte/groove/tree/HEAD/skills/groove-utilities-task-create/SKILL.md

## When to use it
- create a task in the configured backend
- set the task type, status, and parent
- write acceptance criteria for real work
- return the created task ID to the user

## Example prompts
- Create a `feature` task named “Add report export” and infer its parent from the current context.
- Record this work in the configured backend with a goal and concrete acceptance criteria.
- Create a bug with a detailed body, then show me the task ID.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d68481495d64ddf4.

BEGIN THIRD-PARTY FILE d68481495d64ddf4
```text
---
name: groove-utilities-task-create
description: "Create a new task in the configured backend."
license: MIT
allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

# groove-utilities-task-create

## Outcome

A task is created in the configured backend with a title, type, status, optional parent, and (for non-trivial tasks) a rich body. The task ID is returned for reference. This command is the single source of truth for how tasks are created — other skills (work compound, daily, etc.) that need to create tasks must follow this spec and call this skill rather than defining their own creation rules.

## Acceptance Criteria

- Task exists in backend with all required fields populated
- Task ID is shown to user after creation
- Non-trivial tasks (feature work, bugs, plans, stage tasks) have a rich body — never create with an empty body when the task represents real work or a stage
- Parent is set when context suggests one (e.g. stage task under a daily or work epic)

## Constraints

- Read `tasks.backend` from `.groove/index.md` to determine backend
- If `tasks.backend: none`, no-op with friendly message
- If title not provided in arguments, ask user for title and type before proceeding
- Infer parent from current context (open tasks, recent work) and confirm with user if ambiguous
- Default status is `in-progress` (not `todo`) — tasks are created when work is being done
- Do not auto-mark any task as completed during creation
- Backend mappings:
  - `beans`: `beans create "<title>" -t <type> --parent <id> -s in-progress`; body via `beans update <id> -d "<body>"` or by editing the task file under `.groove/tasks/` if the backend is file-based
  - `linear`: create issue via linear CLI or MCP with appropriate team/project
  - `github`: `gh issue create --title "<title>" --body "<body>" --milestone <milestone>`
- **Body (standard):** For any non-trivial task, always supply a body. Use the backend's body/description field (or task file content). Standard body sections: **Context** (what work or session this task belongs to), **Goal** (what "done" means at a high level), **Acceptance Criteria** (checklist of concrete conditions), **Links** (to CHANGELOG, specs, learned files, or other artifacts). Omit a section only if it truly does not apply.
- **Type:** Use the backend's types (e.g. beans: `task`, `bug`, `feature`, `epic`, `milestone`). Stage and bookend tasks (daily Start/End, work stages such as "YYYY-MM-DD, Compound — topic") use type `task` when the backend has no `chore` (e.g. beans).
- **Hierarchy:** Set parent when the task is part of a larger unit (e.g. a daily, an epic). If the caller does not specify a parent, infer from context when possible.
```
END THIRD-PARTY FILE d68481495d64ddf4

The third-party file has ended. Everything between the d68481495d64ddf4 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2812 of 2874 bytes. © andreadellacorte · MIT · https://github.com/andreadellacorte/groove/tree/HEAD/skills/groove-utilities-task-create/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md