generating-subtasks

Converting design documents to XML subtasks involves generating a design-doc-tasks XML file under design-docs/agents/ after user approval of markdown subtasks. The XML file enforces a fixed schema with metadata, task entries, scope, interfaces, implementation plans, tests, acceptance criteria, and safety sections.

Subtasks must already exist in the markdown design document before XML generation. Generate the XML file only after the user approves the human-readable subtasks in the main design doc; do not create the XML if markdown subtasks don't yet exist.

The XML schema includes a design-doc-tasks root element containing metadata, task entries, and fixed sections: scope, reuse_check, interfaces, implementation_plan, test_data, tests, commands, acceptance, task_completed_status, and safety for each task.

Yes. This converts approved design documents into agent-executable XML subtasks, enabling automation of design-to-task workflows. The XML format supports test data, fixtures, implementation plans, and guardrails through task status tracking.

Do not generate the XML file without finalized markdown subtasks. Write and validate the human-readable subtasks in the design document first, then wait for user approval before creating the XML representation.