aim-create-tasks

To convert an approved user intent into a task spec, this skill formulates a structured five-part Task Spec encompassing Title, Assumptions, Goal vs Non-Goal, Core Path, and Value Alignment for submission to the /tasks endpoint.

A five-part Task Spec is a structured task definition format comprising Title, Assumptions, Goal vs Non-Goal, Core Path, and Value Alignment, designed to standardize approved user intents before posting to /tasks.

Yes, you need a valid project_id to create AIM tasks. The skill requires this context to verify alignment with the project's global_provider_id and global_model_id before generating candidate Task Specs.

To verify a candidate Task Spec before posting to /tasks, you submit the drafted five-part spec to aim-verify-task-spec for independent validation to ensure it meets all requirements prior to creation.

No, this skill cannot schedule or execute tasks automatically. It strictly generates candidate Task Specs from approved intents and defers scheduling and execution to other specialized workflow components.

You should not use automated task spec generation when the user intent is unapproved or when project parameters like global_provider_id and global_model_id are undefined, as explicit approval and valid project context are mandatory.