gsd-ui-phase

Automating UI design contract generation for frontend phases involves orchestrating research and validation workflows to produce a validated UI-SPEC.md file. This skill coordinates a multi-role pipeline between a UI researcher and a checker to enforce design constraints and acceptance criteria automatically.

A UI-SPEC.md is a comprehensive design contract describing principles, constraints, and acceptance criteria for a frontend phase. In frontend orchestration, it works by serving as a gated artifact validated between researcher and checker roles to ensure alignment before development.

To generate a UI specification for an unplanned phase, omit the phase number to let the workflow auto-detect and advance. The system then triggers the researcher role to gather requirements, drafts the UI-SPEC.md, and invokes the checker role to verify the contract before completion.

Yes, you can use phase numbering to control frontend workflow advancement by providing a specific phase number. The workflow supports phase-driven execution, automatically advancing to the next unplanned phase once the current UI-SPEC.md is validated and completed.

The UI design contract workflow validates requirements before completion by orchestrating a gated pipeline between a researcher and a checker. The researcher gathers UI aspects while the checker verifies the generated UI-SPEC.md against execution context and phase-handling rules.

Limitations of automated UI specification generation include strict dependency on the execution context and specific researcher-checker orchestration rules. If the upstream requirements are incomplete, the gated validation may fail to produce a valid UI-SPEC.md for the frontend phase.