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