code-task-generator

To turn rough ideas into structured code-task plans, provide a free-form description or a PDD plan path. The skill detects the input type and generates standardized .code-task.md files with required metadata and acceptance criteria.

PDD plan input for automated code task generation is a structured planning document path that the skill reads to automatically produce formatted .code-task.md files, translating vague concepts into concrete tasks and test criteria.

Yes, you can generate code-task files directly from free-form text descriptions. The skill features automatic input type detection, determining whether your input is a free-form description or a PDD plan, and formats the output accordingly.

Yes, you need to approve the task breakdown before code-task file generation. The skill provides a task breakdown and sequence first, awaiting your explicit approval before creating the ready-to-run task documents.

The best way to standardize software engineering task formats is using a fixed Code Task Format. This skill enforces that structure, validating input modes and outputting ready-to-run task documents to ensure rapid, consistent planning.

A limitation of using a fixed Code Task Format is that the skill enforces this specific structure strictly. It targets software engineering workflows, so inputs outside this scope or formats deviating from the standard may not validate correctly.