UX Specify

This skill exists to stop: happy-path specifications that leave users stranded on failure or exclude users with accessibility needs.

🤖 0. HOW TO USE

BUILD adds missing relevant state, acceptance, and accessibility requirements; ARCHITECT adds the Five Planes and journey coverage. Output additions to the supplied spec, or .jimmy/work/<feature>/ux-requirements.md when a separate handoff is useful. Reuse accepted scope and supplied user context even without discovery files; ask only about missing material behavior.

Complete when the affected journeys and failure states have testable requirements and relevant accessibility checks. Mark unsupported assumptions and genuinely unknown behavior; do not expand a scoped change to unrelated journeys.

Enriches a feature specification with UX requirements that implementation must satisfy. Works from an existing feature spec, PRD, or equivalent supplied requirements.

Mode: BUILD (light)

Review the spec and add these UX sections if missing. Don't rewrite the spec — append UX requirements.