workflow-design-interviewlisted

# workflow-design-interview Drive a depth-first design discovery interview against a single requirement. Read the requirement and any existing design system, then walk a one-question-at-a-time conversation with the user until the product's **visual language** and **information architecture** are both locked. Once the user approves, compose a dispatch prompt for the publisher agent that will materialize the artifacts. This skill **writes nothing** — no `overview.md`, no `tokens.md`, no `components.md`, no `accessibility.md`, no `surfaces.md`, no `docs/ui-contract/*.yaml`, no `CLAUDE.md` edit, no commit. The lock (step 7) and approval request (step 8) are bookkeeping in conversation context only; the artifacts themselves are written downstream by a separate publisher agent (the `doc-writer`, named by the orchestrator at invocation time). `ui-ux-pro-max` is the **toolbox** for this interview, not a replacement: its 50+ styles, 161 palettes, font pairings, UX guidelines, and product-type patterns are the option-space you draw on when presenting visual-language recommendations. Load it before the style / palette / typography / component questions. ## When to activate Activate this skill whenever: - A requirement at `docs/product-requirement-document/<feature-name>/requirement.md` (or a greenfield product seed) needs its visual language and information architecture locked before any design artifact is written. - The user types `/workflow-design-interview`, or phrases like 'lo