---
name: ux-discovery
description: Use when clarifying user goals, evidence, or product questions.
---

# Ux Discovery

Out of scope: implementation-ready changes with a clear user task, settled product decision, and sufficient evidence; proceed with the owning implementation Skill.

## Workflow
1. Clarify user goal, audience, context, constraints, current journey, and evidence already available. Separate observed facts from assumptions.
2. Inspect existing screens, routes, content, and analytics/research artifacts the user supplied; do not invent personas or user research.
3. Choose the lightest method for the unresolved question. Hand off taxonomy and findability to `information-architecture`; use `journey-mapping` for end-to-end experiences and distinguish it from in-product flows.
4. When a method recommendation relies on a linked research or practitioner source, cite its exact source ID and relevant access limit; when the choice is design judgment, label it instead of implying research support. Show the proposed structure or path, alternatives considered, rationale, assumptions, and open questions.
5. Define how to validate with representative users or observable behavior.

For evidence boundaries and examples, read `references/discovery.md`. Skip full discovery when the task and evidence are already clear; use `interface-layout` for composition, `visual-hierarchy` for scan order, and `forms-input` or `interaction-patterns` for concrete control behavior.