ux-spec-author

Translate UX design intent into measurable constraints and testable acceptance criteria.

50|9|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Agile-V/agile_v_skills --skill ux-spec-author
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: ux-spec-author
Source: https://github.com/Agile-V/agile_v_skills/tree/main/ux-spec-author
Command: npx skills add https://github.com/Agile-V/agile_v_skills --skill ux-spec-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts UX/design intent into structured, codified requirements that feed engineering and QA. It ensures accessibility, performance budgets, and edge cases are defined early to prevent rework.

Core Features & Use Cases

  • Translate wireframes, flows, and research into measurable constraints and acceptance criteria.
  • Generate DESIGN.md with user flows, interaction patterns, and accessibility/performance budgets.
  • Produce Candidate REQs and a clear handoff protocol to requirement-architect and test designer.

Quick Start

Provide DESIGN.md for a given design to produce testable constraints and handoff artifacts.

Frequently Asked Questions about ux-spec-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate UX wireframes and flows into testable design specs?ā–¼

To turn UX wireframes into testable design specs, you convert design intent into measurable constraints and acceptance criteria. This produces a DESIGN.md file covering user flows, interaction patterns, accessibility, and performance budgets for engineering and QA.

What is the best way to define accessibility requirements from UX research?ā–¼

The best way to define accessibility requirements from UX research is to apply measurable design constraints early, mapping them to edge-case coverage and performance budgets. This creates traceable candidate REQs ready for requirement-architect handoff.

How do I generate a DESIGN.md file with performance budgets and interaction patterns?ā–¼

You generate a DESIGN.md file with performance budgets and interaction patterns by processing UX design intent, flows, and research. The output codifies these elements into structured, testable acceptance criteria for downstream engineering teams.

Does this approach to UX design specs support handoff to requirement-architect and test designer?ā–¼

Yes, this approach supports handoff to requirement-architect and test designer by producing a clear handoff protocol. It outputs candidate REQs, DESIGN.md, and traceability links, ensuring engineering and QA receive structured, testable inputs.

Why define performance budgets and edge cases during UX design spec creation?ā–¼

You define performance budgets and edge cases during UX design spec creation to prevent engineering rework. By codifying these constraints early, the design specs ensure accessibility and performance are testable before development begins.