user-flow

Map complete user journeys with decisions, roles, and state transitions.

13|3|Updated Mar 27, 2026

Search Tags:#onboarding #ux-design #journey-mapping #user-flow #decision-tree #flow-diagrams #multi-role

Ready to run

npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill user-flow-heaptracetechnology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-flow
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/designer/user-flow
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill user-flow-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map and document complete user journeys from entry to exit, including decisions, roles, and state transitions.

Core Features & Use Cases

End-to-end flow mapping: entry points, decision points, and state transitions.
Multi-role scenarios: admin, learner, guest, and other roles; annotate role-specific steps.
Error handling: define happy path and error paths with recovery outcomes.
Flow validation: align with business rules, UX goals, and acceptance criteria.

Quick Start

Provide a complete user flow for a feature by outlining entry points, happy paths, error paths, and multi-role considerations.

Frequently Asked Questions about user-flow

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

FAQPage Schema

What is a complete user flow mapping process for feature onboarding?▼

User flow mapping documents journeys from entry to exit, capturing decision trees, state machines, and role-specific steps for feature onboarding. It defines explicit entry points, happy paths, error paths, and API touchpoints to support scalable UX design.

How do I map multi-role user journeys for admin and guest scenarios?▼

Map multi-role user journeys by annotating role-specific steps for admin, learner, and guest views within the flow. Differentiate each role's decision points, state transitions, and route maps to ensure accurate end-to-end flow validation across all user types.

How do I document error paths and happy paths when debugging UX bottlenecks?▼

Document error paths and happy paths by outlining explicit entry points and defining recovery outcomes for each error state. Map decision trees and state transitions to align flow validation with business rules and UX acceptance criteria when debugging bottlenecks.

Can I use flow diagrams to validate checkout processes against business rules?▼

Flow diagrams validate checkout processes by aligning state transitions and decision trees with business rules and UX goals. Mapping explicit entry points, route maps, and API touchpoints ensures the checkout flow meets defined acceptance criteria.

What is the best way to structure state machines for end-to-end journey mapping?▼

Structure state machines for journey mapping by defining explicit entry points, happy paths, error paths, and API touchpoints. Integrate decision trees and route maps to document complete user flows from entry to exit accurately.

Do I need API touchpoints defined to map UX onboarding flows?▼

Defining clear API touchpoints is required to map UX onboarding flows and support scalable design work. Explicit touchpoints align state transitions and route maps with the technical constraints of the feature onboarding process.