product-design-flows

Transform requirements and user stories into visual user journeys and interaction flows.

37|5|Updated Nov 18, 2025

Search Tags:#user experience #flows #journey #story-mapping #breadboard

Ready to run

npx skills add https://github.com/BellaBe/lean-os --skill product-design-flows

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-design-flows
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/product-design-flows
Command: npx skills add https://github.com/BellaBe/lean-os --skill product-design-flows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts requirements and stories into user journeys and interaction flows.

Core Features & Use Cases

User journey maps: AWARE → CONSIDER → ACQUIRE → USE → SUCCEED
Breadboards: Visual flow sketches
Happy path: Define ideal flows

Quick Start

Provide user stories; returns a journey map.

Frequently Asked Questions about product-design-flows

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

FAQPage Schema

How do I convert user stories into journey maps?▼

User journey maps visualize the stages a user progresses through—AWARE, CONSIDER, ACQUIRE, USE, SUCCEED—transforming requirements and stories into a continuous narrative. Provide user stories as input; the Skill returns a structured journey map showing each stage, user actions, and outcomes.

What's the difference between journey maps and breadboard flows?▼

Journey maps show the end-to-end user experience across stages and touchpoints. Breadboards are visual flow sketches that detail interaction sequences and decision points. Use journey maps for high-level experience design and breadboards for interaction-level wireframing and flow validation.

How do I define happy-path and error flows for a feature?▼

Happy-path flows map the ideal user journey through a feature with no obstacles; error flows document what happens when conditions fail or edge cases occur. The Skill generates both flow types from requirements, including state diagrams and edge-case handling to ensure complete interaction coverage.

Can I use this to map customer journeys across product development?▼

Yes. Journey mapping applies across product development, feature design, and UX validation. It transforms functional and technical requirements into visual customer workflows and interaction sequences, supporting both planning phases and validation of new features.

What input do I need to create user flows and journey maps?▼

Provide user stories, requirements, and business context. The Skill generates journey maps, breadboard-style diagrams, state transitions, and edge cases. Templates for stages, actions, states, and preconditions structure the output for design handoff and stakeholder review.