bmad-agent-ux-designer

To turn product requirements into UX design specifications, you apply persona-driven analysis to define user flows, edge cases, and interface behaviors. This produces structured documentation that shapes architecture and provides clear implementation guidance.

Defining user flows and edge cases requires analyzing product goals and story context to clarify user journeys and decision points. Mapping interface behavior during planning ensures engineers build with confidence and clear design constraints.

Persona-driven analysis improves interaction design by applying empathy for user needs to resolve unclear handoff decisions. It translates vague feature concepts into opinionated UX intent, feeding architecture and implementation with specific behaviors.

Yes, you can generate wireframes and behavior definitions directly from a PRD by extracting product goals and story context. The specification writing process synthesizes these inputs to document decision points and design constraints for engineers.

Yes, you need structured product documentation like PRDs and story context to define UX direction effectively. Clear product goals provide the necessary foundation for analyzing empathy and user needs to produce practical design specifications.

Unclear interaction design causes handoff problems because engineers lack the opinionated UX intent needed to build features accurately. Without defined user flows and edge cases, teams are left with vague ideas that fail to shape implementation.