bmad-ux

Plan UX specifications and interaction contracts for web, mobile, and multi-surface products.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-ux-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-ux
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-ux
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-ux-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It turns rough product ideas, scattered notes, and incomplete requirements into structured UX direction that downstream teams can actually build from.

Core Features & Use Cases

  • UX discovery and facilitation: Gathers the user's goals, constraints, and context before shaping the experience.
  • Design and experience spines: Produces a visual identity spine and a behavioral experience spine that stay aligned and resolve conflicts cleanly.
  • Workflow support: Helps plan information architecture, user journeys, component behavior, states, accessibility, and responsive behavior for web, mobile, and multi-surface products.
  • Practical use case: Use it when you need to transform a product brief into clear UX specifications, validate an existing experience structure, or prepare handoff-ready design artifacts.

Quick Start

Ask the bmad-ux skill to plan the UX for your product by describing the goal, platform, users, and any constraints you already know.

Frequently Asked Questions about bmad-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn rough product ideas into clear UX specifications?

To turn ideas into clear UX specifications, you need a structured discovery process that defines goals, constraints, and context. This creates aligned design and experience spines for information architecture, user flows, and states.

What is the best way to plan information architecture and user flows for a mobile product?

Planning information architecture and user flows for mobile products involves mapping user journeys and component behaviors. It requires creating a behavioral experience spine that validates accessibility and responsive layout decisions.

How do I validate an existing experience structure and interaction design?

Validating an existing experience structure requires cross-referencing design and experience spines against user goals. This ensures validation-aware coverage of interaction design, states, and accessibility without inventing missing requirements.

Can I use UX design specifications for multi-surface products?

Yes, UX design specifications can be created, updated, and validated for multi-surface products. They capture layout decisions, voice, and user states across web and mobile platforms within a unified design and experience spine.

Do I need complete product requirements before planning UX workflows?

No, you do not need complete product requirements before planning UX workflows. The process uses structured discovery to gather goals and constraints, capturing design decisions through optional creative artifacts without inventing missing requirements.