What problem does it solve? Writing UX specifications screen by screen is slow and often inconsistent, and teams frequently mix visual design details into UX docs. This Skill runs a structured interview that captures content, actions, states, and navigation for every screen, then writes clean Markdown files to docs/03_design/. ## Core Features & Use Cases - Screen-by-screen interview: Walks through each screen one at a time, capturing what the user sees, available actions, action outcomes, and empty/loading/error/partial states. - Cross-screen flow documentation: Records multi-screen flows with triggers, steps, decision points, and failure states in a dedicated ux_flows.md file. - Context-aware setup: Reads existing PRD, personas, product journey, and domain model docs before asking questions, and auto-detects the docs folder. - Use Case: After defining personas and a product journey for a finance app, run this Skill to produce ux_dashboard.md, ux_account_detail.md, and ux_flows.md covering every screen and the payment flow, ready to hand to a UI designer. ## Quick Start Ask the assistant to create a UX specification for your product using the ux-spec skill and answer the screen-by-screen interview questions.
