Premium Web Build Gate
Check that a new premium build or substantial redesign has enough agreed direction to implement reliably. Fill the actual decision gaps while preserving the requested quality tier, real content, accessibility, responsive behavior and verification requirements.
Scope first
- Reuse an adequate existing brief, blueprint, design system and approved stack. Do not recreate them because this skill was selected.
- For a localized change, check only the affected requirements and proceed to its implementation owner. A typo or component fix does not require a whole-site spec or reference-research project.
- For a review-only request, return findings or a proposed spec and remain read-only.
- Continue routine reversible work within existing authorization. Ask only for a consequential unresolved choice that cannot be inferred or handled with a reasonable reversible assumption. Preserve real release and client-approval boundaries.
Resolve missing decisions
Read the build-ready specification guide for the relevant content, visual, motion, tooling and QA criteria when a new build or substantial redesign has unresolved decisions. Use only the applicable fields; no fixed number of references, new document or additional skill installation is required.
Use the shared quality tiers when the delivery depth is unclear. An installed route-sellable-web-tier specialist is optional; the bundled reference is sufficient when it is absent.
Complete and verify
Once direction is adequate, continue the requested implementation through running, inspecting, correcting and validating affected behavior. Preserve source truth, the selected stack and supported accessibility/reduced-motion behavior. Existing project release gates remain applicable.
For an audit, report the specific gaps and their evidence. For implementation, report changed files and checks actually performed. A completed spec alone is not a completed website, and unperformed browser or production checks remain unverified.
