plan-generate

To generate .pipeline artifacts from an approved milestone plan, provide the plan to the Skill to automatically produce prompts, config.yaml, architecture baselines, and cycle metadata.

Hypo-Workflow architecture baselines and prompts require an approved milestone plan to generate the necessary .pipeline/prompts directory, config.yaml, and cycle.yaml files.

Cycle.yaml preserves technical routes and research evidence by capturing workflow_kind, lifecycle policies, and continuation points from the approved milestone plan for downstream execution.

Yes, you can automate pipeline configuration generation for build and showcase workflows by processing milestone details to create config.yaml and cycle.yaml with the correct lifecycle metadata.

Yes, you need an approved milestone plan because the generation of .pipeline/config.yaml relies on interactive plan fields and lifecycle metadata extracted from the plan.

The best way to preserve audit focus and risks in pipeline config is to generate artifacts from a milestone plan that explicitly retains technical routes, research evidence, and audit focus data.