compile-design-spec

A UX design specification consolidates personas, screens, and user flows into a single self-contained document. It embeds Mermaid flow diagrams and references design system paths to ensure architecture and implementation teams receive exhaustive traceability during handoff.

The best way to generate a decision manifest is to consolidate UX artifacts into a design specification. This process automatically emits a decision-manifest.yaml file that records newly inferred design decisions, enabling orchestrator-driven surfacing of grounded architectural choices during handoff.

You compile user flows and accessibility targets by reading input markdown frontmatter, scope.yaml, and quality-profile.yaml files. The process aggregates these inputs to produce a comprehensive design-spec.md that ensures complete accessibility coverage and end-to-end traceability for implementation handoff.

Yes, you can reference a design system by path without copying token values into the compiled design spec. The specification consolidates UX artifacts while linking to the design-system.md, maintaining a single source of truth for visual styles and tokens during architecture handoff.

Compiling a UX design specification requires designer outputs rooted at the product base path, including personas.md, screen markdown files, flow definitions, scope.yaml, quality-profile.yaml, and design-system.md. These inputs ensure exhaustive traceability and accessibility coverage in the final handoff document.