groove-utilities-task-create：统一任务创建工具，支持Beans、Linear、GitHub后端

groove-utilities-task-create by andreadellacorte/groove

78 周安装量

4 GitHub Stars

GitHub

安装命令

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

项目管理自动化命令行工具

🇨🇳中文介绍

groove-utilities-task-create

产出

在配置的后端中创建一个任务，包含标题、类型、状态、可选的父任务，以及（对于非琐碎任务）一个详细的任务正文。返回任务ID以供参考。此命令是任务创建方式的唯一标准来源——其他需要创建任务的技能（work compound、daily 等）必须遵循此规范并调用此技能，而不是定义自己的创建规则。

验收标准

任务存在于后端，且所有必填字段均已填充
创建后向用户显示任务ID
非琐碎任务（功能工作、缺陷、计划、阶段任务）具有详细正文——当任务代表实际工作或一个阶段时，切勿创建空正文的任务
当上下文暗示存在父任务时（例如，daily 或工作史诗下的阶段任务），设置父任务

约束

从 .groove/index.md 读取 tasks.backend 以确定后端
如果 tasks.backend: none，则无操作并显示友好提示信息
如果参数中未提供标题，则在继续之前询问用户标题和类型
从当前上下文（打开的任务、最近的工作）推断父任务，如果存在歧义则与用户确认
默认状态为 in-progress（而非 todo）——任务是在工作进行时创建的
创建过程中不要自动将任何任务标记为已完成
后端映射：
- beans: ；正文通过或（如果后端是基于文件的）通过编辑下的任务文件来添加

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

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

Weekly Installs

Repository

andreadellacorte/groove

GitHub Stars

First Seen

8 days ago

Security Audits

Gen Agent Trust HubPass SocketFail SnykPass

Installed on

opencode42

gemini-cli42

github-copilot42

codex42

kimi-cli42

cursor42

groove-utilities-task-create：统一任务创建工具，支持Beans、Linear、GitHub后端

🇨🇳中文介绍

groove-utilities-task-create

产出

验收标准

约束

相关 Skills

🇺🇸English

groove-utilities-task-create

Outcome

Acceptance Criteria

Constraints

最新 Skills