UX Discovery

This skill exists to stop: design decisions based on invented user behavior or unexamined category assumptions.

🤖 0. HOW TO USE

Select BUILD for missing context in a scoped feature, ARCHITECT for substantial discovery, or research for category benchmarks. For interview planning, load User Interview Design. Output context notes, evidence-grounded personas/journeys, a research plan, or category benchmarks under .jimmy/work/<feature>/ as needed for the handoff; small answers may stay inline.

Reuse supplied context, accepted research objectives, and prior evidence. Ask only missing questions that affect the decision; absent artifact files do not require repeating discovery. User interviews are conducted by people or separately authorized research tools: a plan is not a completed study. Never invent participants, findings, verbatim quotations, or measurements. Label synthesized personas and emotional arcs as hypotheses unless supported by evidence; quotations require an actual source.

Gathers user context to ground specifications in real user behavior rather than developer assumptions. Supports the current elicitation or analyst work when user context is missing.

Mode: BUILD (light)

Add these UX-focused questions to the elicitation, woven into the normal elicitation flow. Don't extend the time — make the existing questions sharper.

Ask about the user's context (pick 2-3 most relevant):