bs-ux

Generate user journeys, screen inventories, and ASCII wireframes from MVP scope.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bs-ux
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/brainstorming/skills/bs-ux
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about bs-ux

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

FAQPage Schema
How do I generate user journeys and wireframes from MVP requirements?

Generate user journeys and wireframes from MVP requirements by processing must-have feature lists to produce persona-driven flows, screen state tables, and ASCII wireframe layouts. The tool reads product scope documents and outputs structured Markdown files detailing each feature's journey steps and screen states.

What are screen states in UX design and how do I document them for an MVP?

Screen states in UX design define the various UI conditions such as default, empty, loading, error, and success states. Document them for an MVP by enumerating all screens and generating state tables that cover realistic edge cases beyond the standard happy path, ensuring comprehensive design coverage.

Can I create ASCII wireframes for onboarding flows directly from product scope documents?

Yes, you can create ASCII wireframes for onboarding flows directly from product scope documents. The skill processes MVP must-have features and persona definitions to generate textual wireframes that communicate layout and component placement for onboarding paths and other primary screens.

What is the best way to map persona-driven user journeys to screen inventories?

Map persona-driven user journeys to screen inventories by defining a named journey with a specific persona and objective for each must-have feature, then translating those journey steps into an enumerated list of screens with defined states. This produces actionable UX artifacts ready for team handoff.

Does generating textual wireframes require prior design tool experience?

Generating textual wireframes does not require prior design tool experience because the outputs are text-based ASCII layouts saved as Markdown files. This approach fits text-first workflows and allows product managers and developers to iterate on layout and component placement without visual design software.

Why use ASCII wireframes instead of visual wireframes for UX handoff?

Use ASCII wireframes for UX handoff to quickly communicate layout and component placement in text-first workflows without depending on visual design software. Textual wireframes are easily exportable, version-controllable Markdown files that eliminate ambiguity about screen states and entry points during product and engineering handoffs.