القائمة
Create a new task in the configured backend.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
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.
Set up task backend and configuration.
Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.
Install groove's Cursor native hooks into .cursor/hooks.json. Enables compaction-safe re-priming, session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.
Run all groove health checks: config, backends, companions, AGENTS.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"} |
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.
tasks.backend from .groove/index.md to determine backendtasks.backend: none, no-op with friendly messagein-progress (not todo) — tasks are created when work is being donebeans: 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-basedlinear: create issue via linear CLI or MCP with appropriate team/projectgithub: gh issue create --title "<title>" --body "<body>" --milestone <milestone>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).