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, pl…