plan-dev-create

To generate a development plan from approved Plan Tests, apply a plan generator that reads TC-N, SVC-N, and REQ-N inputs to produce a TASK-N payload with subtasks, cross-service dependencies, and issue mapping.

A TASK-N payload in cross-service task management is a structured output containing five fields, subtasks, cross-service dependencies, and issue mapping, generated from Plan Tests, Design, and Discussion inputs.

You need to map issues to services and their interfaces after Plan Tests are approved and reach the WAITING state, allowing you to determine implementation tasks and cross-service dependencies.

To create implementation tasks from Design and Discussion requirements, read the SVC-N and REQ-N inputs, clarify requirements, and generate a TASK-N payload with subtasks and cross-service dependencies.

Yes, this plan generation workflow requires approved Plan Tests in a WAITING state to determine implementation tasks and map them to services and their interfaces.

The limitation of generating development plans from Plan Tests is that the workflow strictly requires prior approval of TC-N, SVC-N, and REQ-N inputs to produce the TASK-N payload with cross-service dependencies.