plan-dev-create

To turn test specs into a development plan, you need an automated workflow that reads Plan Tests and generates structured TASK-N items with sub-tasks and cross-service dependencies. This process applies when a WAITING Plan Test exists and requires mapping Issues to actionable dev tasks.

Generating development tasks from approved Plan Tests involves reading Design and Discussion inputs to output structured TASK-N items. Each task requires five specific fields, sub-tasks, and cross-service mappings to ensure comprehensive coverage of the implementation requirements.

Yes, you can map cross-service dependencies when creating a dev plan by applying automation that reads parent Plan Tests. The generated TASK-N items explicitly include cross-service mappings to ensure all architectural dependencies are documented before implementation begins.

Automated task generation requires Plan Tests, Design, and Discussion inputs to produce a structured dev plan. The workflow triggers when a WAITING Plan Test exists, reading these inputs to generate TASK-N items with five fields and sub-tasks.

Yes, automated plan generation works with sub-tasks and Issue mapping by processing WAITING Plan Tests. The output creates structured TASK-N items that include five fields, nested sub-tasks, and explicit Issue mappings to fully define the dev scope.

A key limitation of generating dev plans from Plan Tests is that the workflow only applies when a WAITING Plan Test exists. If the test status is not WAITING, or if Design and Discussion inputs are missing, the automated task generation cannot proceed.