groove-utilities-task-create

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

在已配置的后端中创建包含标题、类型、状态、可选父任务，以及（针对非琐碎任务的）富文本内容的任务。执行后会返回任务ID供参考。本命令是任务创建的唯一权威来源——其他需要创建任务的技能（复合工作、日常任务等）必须遵循此规范调用本技能，而不得自行定义创建规则。

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)

后端中存在填充了所有必填字段的任务
创建完成后向用户展示任务ID
非琐碎任务（功能开发、bug、计划、阶段任务）必须包含富文本内容——当任务代表实际工作或工作阶段时，永远不要创建内容为空的任务
当上下文暗示存在父任务时，需设置父任务（例如：日常任务或工作史诗下的阶段任务）

Constraints

约束条件

Read
```
tasks:
```
from
```
.groove/index.md
```
to determine backend
If
```
tasks: 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/index.md
```
中的
```
tasks:
```
配置确定后端
如果配置为
```
tasks: none
```
，执行空操作并返回友好提示
如果参数中未提供标题，继续操作前需询问用户标题和类型
从当前上下文（已打开的任务、最近的工作）推断父任务，若存在歧义需与用户确认
默认状态为
```
in-progress
```
（而非
```
todo
```
）——任务在工作进行时创建
创建过程中不要自动将任何任务标记为已完成

后端映射规则：

beans

：

beans create "<title>" -t <type> --parent <id> -s in-progress

；如果后端是文件存储类型，可通过

beans update <id> -d "<body>"

或编辑

.groove/tasks/

下的任务文件添加内容

```
linear
```
：通过linear CLI或MCP创建对应团队/项目下的issue

github

：

gh issue create --title "<title>" --body "<body>" --milestone <milestone>

正文（标准）：任何非琐碎任务都必须提供正文，使用后端的正文/描述字段（或任务文件内容）。标准正文章节包括：上下文（本任务所属的工作或会话）、目标（高层级的“完成”定义）、验收标准（具体条件的检查清单）、链接（指向CHANGELOG、规范、已学习的文件或其他产物）。仅当某个章节确实不适用时才可省略。
类型：使用后端支持的类型（例如beans的类型：
```
task
```
、
```
bug
```
、
```
feature
```
、
```
epic
```
、
```
milestone
```
）。当后端没有
```
chore
```
类型时，阶段和首尾任务（每日开始/结束、工作阶段如“YYYY-MM-DD, Compound — 主题”）使用
```
task
```
类型（例如beans后端）。
层级：当任务属于更大的工作单元（例如日常任务、史诗）时需设置父任务。如果调用方未指定父任务，尽可能从上下文推断。
始终向用户回显创建的任务ID和标题