groove-utilities-task-create

Create a new task in the configured backend.

跳到安装

仓库: andreadellacorte/groove
最近来源活动: 2026年3月9日 19:59
检测到的 SKILL.md 语言: 英语
星标: 5
分支: 0

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/andreadellacorte/groove --skill groove-utilities-task-create

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

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.
Always echo the created task ID and title back to the user

返回搜索返回安装

groove

Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.

2026-07-04

groove-admin-claude-statusline

Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.

2026-07-04

groove-utilities-task-install

Set up task backend and configuration.

2026-06-10

查看这个仓库的全部 Skills

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

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.
Always echo the created task ID and title back to the user

groove-utilities-task-create

来源信息

安装方式

检查来源文件

groove-utilities-task-create

Outcome

Acceptance Criteria

Constraints

同仓库更多 Skills

groove-utilities-task-create

Outcome

Acceptance Criteria

Constraints

同仓库更多 Skills