cy-create-tasks

Place your _prd.md and optionally _techspec.md in .compozy/tasks/<feature-name>/, then invoke the skill with the feature name. It decomposes requirements into granular tasks with dependencies, complexity ratings, and test requirements, presenting the breakdown for your approval before writing files.

The skill reads the TechSpec implementation sections and splits them into independently implementable tasks, each with YAML frontmatter (status, title, type, complexity, dependencies) and enriched sections covering overview, requirements, subtasks, implementation details, and tests.

Yes, but tasks will be higher-level. The skill warns you, derives tasks from PRD functional requirements instead, and relies more heavily on codebase exploration to fill implementation details. If both PRD and TechSpec are missing, it stops and asks you to create one first.

Task files must match the pattern task_\d+.md (e.g., task_01.md) and start with YAML frontmatter containing status, title, type, complexity, and dependencies. Files with the old _task_ prefix are not recognized by Compozy's ParseTaskFile function.

Validation fails when frontmatter fields are missing, dependencies contain circular references, task numbering is inconsistent between _tasks.md and individual files, or required sections like Tests or Deliverables are omitted. Re-run compozy validate-tasks after fixing reported issues until it exits 0.

Do not use it for creating PRDs or TechSpecs themselves, or for directly executing tasks. It only handles the breakdown and enrichment stage between specification writing and task execution.