cy-create-tasks

Provide the feature name and ensure a _prd.md or _techspec.md exists in the tasks directory. The Skill decomposes requirements into granular tasks with complexity ratings and dependencies, presents the breakdown for approval, then writes a master task list and individual task files.

Place _techspec.md in the feature's tasks directory and invoke the Skill with the feature name. It derives tasks from TechSpec implementation sections, enriches them with codebase exploration, and writes task_01.md through task_N.md files.

Yes, tasks can be derived from the PRD alone, but they will be higher-level without implementation guidance. The Skill warns about this, relies more on codebase exploration for details, and flags missing implementation gaps instead of inventing specifics.

Circular dependencies are prohibited by design. Each task must be independently implementable once its declared dependencies are met, and no task may depend on another task that directly or transitively depends back on it.

Do not use it for PRD creation, TechSpec generation, or direct task execution, as those are outside its scope. It also stops and asks for input when neither a PRD nor TechSpec exists, since it requires at least one requirements source.