ring-validating-ux-completeness

name

ring:validating-ux-completeness

description

Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer pass and before the TRD when the feature has UI; the pre-dev orchestrators recommend it when the feature has UI. Use to check UI design completeness. Skip for backend-only, API-only, or no-UI work.

UX Completeness Validation

Standalone utility — not a gate in any pre-dev track. Verifies that UX specifications are COMPLETE before investing in technical architecture. This is a VALIDATION pass — it checks existing artifacts, does not create new ones.

The TRD does not hard-block on this verdict: ring:writing-trds honors design-validation.md if present; if absent, it proceeds and notes the UX risk.

When to use

• Feature has UI and a standalone product-designer run produced UX artifacts
• Before starting the TRD (recommended slot: between PRD and TRD)
• The pre-dev orchestrators recommend it as an optional standalone step when the feature has UI
• User asks to "validate design" or "check if design is complete"

Skip when

• Feature is backend-only with no UI
• Pure API/infrastructure task
• Bug fix with no UX changes

Sequence

Runs before: ring:writing-trds (recommended, not required) Runs after: ring:writing-prds and a standalone product-designer run (ux-validation mode; optionally ux-design mode)

Entry Criteria

Artifact	Location	Required
prd.md	docs/pre-dev/{feature}/