builder-agent

An approved solution-design.md workspace with complete workspace data is required to build and deploy automation assets successfully. Without this approved design input, the structured end-to-end build process cannot validate and generate the deployed components.

When the approved solution-design.md workspace is processed, the agent validates, tests, and packages the delivered automation components, generating an as-built.md file for project closeout after the end-to-end construction finishes.

Yes, you can build templates and configs from a solution-design.md file by providing the approved workspace data to the builder agent, which constructs these automation assets alongside workflows and projects during the end-to-end build process.

The best way to automate handoff from design to deployment is using a builder agent that consumes an approved solution-design.md workspace to construct, validate, and package Itential automation assets without manual coding or intermediate handoffs.

Automation builds fail when the solution-design.md workspace is not fully approved or lacks complete workspace data, which the builder agent requires to validate components and produce the deployed automation assets and as-built documentation.