journey

Design end-to-end user flows, screen sequences, and multi-channel journey maps.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/ishfuseini/usecase-gen --skill journey-ishfuseini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/ishfuseini/usecase-gen/tree/main/agent/skills/journey
Command: npx skills add https://github.com/ishfuseini/usecase-gen --skill journey-ishfuseini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing coherent user experiences across screens, devices, and channels is hard: flows break at decision points, users abandon mid-task, and cross-channel handoffs lose context. This Skill structures the end-to-end design of any user journey so friction, edge cases, and variations are addressed before implementation. ## Core Features & Use Cases - End-to-End Flow Mapping: Designs complete journeys from entry point to outcome, including decision branches, error recovery paths, and re-entry after interruption. - Variation & Device Adaptation: Defines flow variants by user type, entry point, context, and platform (mobile, web, TV, embedded), plus multi-channel journey mapping across email, app, web, and support. - Visualization Output: Produces flow diagrams as self-contained HTML, Figma frames via MCP, or pencil.dev documents, alongside copy specifications and interaction specs. - Use Case: A product designer asks how a new user should experience onboarding. The Skill maps the signup flow screen-by-screen with copy, validation states, mobile and web variants, drop-off metrics, and an HTML diagram of the sequence. ## Quick Start Ask the assistant to design the user flow for a specific task, such as "Design the onboarding journey for new users of our mobile app with a diagram."

Frequently Asked Questions about journey

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

FAQPage Schema
How do I design a user onboarding flow?

Define the user's goal, entry point, and success metric first, then map each screen with its copy, CTAs, and validation states. This Skill structures that process, including progress indicators, error recovery, and re-entry for users who leave mid-flow.

How to map a user journey across multiple channels?

Identify channel transition points where users move between email, app, web, or support, then specify what state must persist at each handoff. The Skill maps these transitions explicitly and designs continuity through deep links and synced progress.

Can the journey skill output a flow diagram in Figma?

Yes. When Figma is selected, the Skill loads the figma-use skill and calls the Figma MCP tool to create flow nodes, arrows, and decision gates as frames. HTML and pencil.dev outputs are also supported.

What is the difference between journey design and wireframing?

Journey design defines which screens exist, their sequence, and what each must accomplish. Wireframing decides the layout within each screen. This Skill owns the flow logic and hands off screen-level layout to the wireframe skill.

When should I not use a single user journey arc?

Avoid one smoothed arc when research shows multiple distinct, non-converging user paths. The Skill maps each path separately to preserve real variance instead of creating false coherence that hides actual user behavior.