gsd-ui-phase

To create a UI spec from an unstructured frontend phase, you need a design contract that validates the phase context and orchestrates research to produce a clear, implementation-ready UI specification.

A UI design contract is a structured specification that validates phase context against workflow gates and brand references before frontend implementation begins, ensuring downstream execution stays aligned with the intended product direction.

UI spec verification involves checking the generated specification file against required workflow gates and brand reference alignments to confirm it satisfies all structural and design constraints before execution.

You do not need to manually define the frontend phase number to generate a UI spec, because the system supports auto-detection of the current phase while allowing manual phase number overrides when necessary.

You can use UI research orchestration to gather design inputs for frontend planning, coordinating research steps end-to-end to collect all necessary information before generating the phase-specific UI specification.

You should avoid using an automated UI spec generator when your frontend planning lacks defined workflow gates or established brand guidelines, as the system requires these references to validate and produce a compliant design contract.