distill

To convert unstructured task text into a structured executable spec, paste raw task descriptions to automatically generate a TASK specification aligned with TASK.schema.md, enforcing frontmatter requirements and validating required sections.

Automating task specification generation for CI checkpoints involves producing a ready-to-use TASK.md from raw text that enforces schema validation, enabling consistent documentation and handoffs directly within your workflow pipelines.

Yes, you can load CODEMAPs for cited paths when generating task specifications by using the optional --group context tag, which enhances context specifically for validation during the transformation process.

To auto-tier engineering tasks by complexity level, the transformation process automatically categorizes raw task text into micro, standard, or full tiers to ensure the resulting executable specification matches the required scale.

The best way to enforce frontmatter requirements in task specifications is to use an automated schema-aligned transformation that validates required sections and guarantees production-ready TASK.md files for engineering handoffs.

No specific dependencies are required to transform raw tasks into executable specifications, as the step-driven workflow independently handles inputs, schema validation, and output generation with optional archiving.