generating-subtasks

Convert approved design documents into agent-executable XML subtasks.

1|1|Updated Dec 18, 2025

Search Tags:#automation #subtasks #XML #design-docs #design-doc

Ready to run

npx skills add https://github.com/SteveBronder/skillrena --skill generating-subtasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generating-subtasks
Source: https://github.com/SteveBronder/skillrena/tree/main/skillrena/generating-subtasks
Command: npx skills add https://github.com/SteveBronder/skillrena --skill generating-subtasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved design documents into agent-executable XML subtasks. This file is generated only after the user approves human-readable subtasks in the main design doc.

Core Features & Use Cases

XML design-doc-tasks schema with metadata, tasks, interfaces, tests, and acceptance.
Supports test data, fixtures, and implementation plan sections.
Enforces guardrails and status tracking through task_completed_status.

Quick Start

After a design doc is approved, place design-docs/agents/<design-doc-name>.xml under the appropriate path.
This file is generated only after the user approves subtasks in the markdown design doc.
If you do not yet have subtasks in the md design doc, do not generate the XML file; write the subtasks in the markdown first, then wait for user instructions.

Frequently Asked Questions about generating-subtasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert design documents into executable XML 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.

What's required before generating the XML subtasks file?▼

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.

What structure does the design-doc-tasks XML file enforce?▼

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.

Can I use this to automate design document processing?▼

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.

What happens if subtasks aren't finalized in the markdown design doc?▼

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.