prototype-builder

Coordinate the full prototype build cycle by enforcing hard-gate requirements, confirming layouts, decomposing components, orchestrating builds, and conducting SME walkthroughs based on an approved Discovery Plan.

A hard-gate requirement in prototype workflow management is an enforced checkpoint ensuring layout confirmation, component decomposition, and discovery plan alignment are completed before advancing the build cycle.

Yes, a Discovery Plan is required before starting a prototype build session. The orchestration workflow applies in exploration sessions where a Discovery Plan exists to drive layout confirmation and component decomposition.

Component decomposition and layout confirmation work by validating the layout direction first, then breaking the prototype into buildable components delegated to specialized sub-skills for execution during the exploration session.

No, you cannot build prototype components directly within this workflow. It coordinates layout confirmation and delegates component building tasks to specialized sub-skills like visual-companion and subagent-driven-prototyping.

Exploration notes and prototype walkthrough captures are written to the exploration/captures directory after completing the build cycle, ensuring all prototype notes and SME feedback are documented.