map-user-flow

Map user journeys across platforms with entry points, screens, decisions, and edge states.

14|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hungv47/meta-skills --skill map-user-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-user-flow
Source: https://github.com/hungv47/meta-skills/tree/main/forsvn-dev/skills/product/map-user-flow
Command: npx skills add https://github.com/hungv47/meta-skills --skill map-user-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maps and validates multi-step in-product journeys across platforms, ensuring consistent flows and comprehensive edge-case coverage.

Core Features & Use Cases

  • End-to-end flow mapping: from entry to exit across screens, decisions, and platform-native touchpoints.
  • Platform surface coverage: explicit per-surface entry points and edge-case handling for each target surface.
  • Artifact-driven handoff: produces per-flow artifacts and wiring for downstream architects and developers.

Quick Start

Invoke the map-user-flow skill to map a new feature's flow across platforms and generate a shareable artifact.

Frequently Asked Questions about map-user-flow

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

FAQPage Schema
How do I map a multi-step user journey across different platforms?

Mapping a multi-step user journey involves identifying entry points, core screens, decisions, and edge states across platforms to produce a shareable artifact. This artifact ensures cross-platform coherence and supports handoff to architecture, product, and QA teams.

What is cross-platform user flow design and when do I need it?

Cross-platform user flow design is the process of charting complete in-product journeys across different surfaces. You need it when validating consistent flows and comprehensive edge-case coverage for features spanning multiple platforms.

How do I document per-surface entry points and edge states for a product flow?

Documenting per-surface entry points and edge states requires defining precise triggers and pre-loaded states for each target surface. This process ensures explicit platform surface coverage and identifies necessary handoffs to downstream skills.

Can I generate shareable artifacts for architecture and QA handoff from a flow map?

Yes, generating a flow map produces per-flow artifacts and wiring specifically designed for artifact-driven handoff. These shareable outputs enable seamless coordination with downstream architects, developers, and QA teams.

Does UX mapping for multi-step journeys handle platform-native touchpoints and decisions?

UX mapping for multi-step journeys explicitly handles platform-native touchpoints and decisions. It charts the end-to-end flow from entry to exit, ensuring all screens and edge cases are accounted for across each target surface.