What problem does it solve?
Translates product requirements and MVP scope into clear user journeys, screen inventories, and textual wireframes so teams can move from concept to actionable UX artifacts without ad hoc guessing. It eliminates ambiguity about entry/exit points, screen states, and primary user interactions that typically block handoffs between product, design, and engineering.
Core Features & Use Cases
- User Journeys per Must-Have: For each Must-Have in brainstorm/04-mvp-scope.md, produce a named journey with persona, objective, and a step-by-step action table.
- Screen Inventory & States: Enumerate screens and define default, empty, loading, error, and success states so designs cover realistic edge cases beyond the happy path.
- Textual ASCII Wireframes: Create clear, exportable ASCII wireframes for primary screens to quickly communicate layout and component placement in text-first workflows.
- Outputs for Handoff: Write consolidated Markdown files (brainstorm/05-ux-flows.md and brainstorm/ux/wireframes.md) ready for review or downstream mapping to technical specs.
- Use Case Example: When preparing an onboarding flow for an MVP, the skill generates persona-aware journeys, lists all screens with states, and supplies textual wireframes that a UX designer or PM can iterate on.
Quick Start
Use bs-ux to generate user journeys, screen state tables, and ASCII wireframes from the MVP items in brainstorm/04-mvp-scope.md and output them to brainstorm/05-ux-flows.md and brainstorm/ux/wireframes.md.