journey

Design end-to-end user journeys with screen flows and success criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/snuffomega/pricechart --skill journey-snuffomega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/snuffomega/pricechart/tree/main/.agents/skills/journey
Command: npx skills add https://github.com/snuffomega/pricechart --skill journey-snuffomega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you design end-to-end user journeys so users can successfully move from an entry point to a clear outcome, including branching decisions, interruptions, and recovery paths.

Core Features & Use Cases

  • End-to-end flow mapping: Define the full sequence of screens/states from arrival to resolution, including what precedes and follows the journey.
  • Variation-aware journey design: Account for differences by user type, device context, entry point, and multi-channel touchpoints.
  • Task analysis & flow optimization: Reduce friction with progressive disclosure, decision-tree simplification, and error prevention/recovery design.

Quick Start

Use the journey skill to design the complete signup-and-onboarding flow for a RetroCache-like product, including the screens, branching logic, error recovery, and how a user resumes if they leave mid-process.

Frequently Asked Questions about journey

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

FAQPage Schema
How do I map a multi-step user flow that handles branching decisions and interruptions?

Mapping a multi-step user flow requires defining the complete sequence of screens and states from entry to resolution, including branching decisions, interruptions, and recovery paths. You can structure task analysis to reduce friction with progressive disclosure and decision-tree simplification.

What is the best way to handle error recovery and resume states in a user journey?

Handling error recovery in a user journey involves designing state transitions that allow users to resume mid-process if they leave. You can minimize friction by implementing progressive disclosure, error prevention design, and measurable success criteria for each interaction transition.

Can I use this approach to design settings wizards and dashboard notifications across multiple touchpoints?

Yes, you can design settings wizards, dashboards, and notifications by defining screen-by-screen flow variations across multi-channel touchpoints. This approach produces interaction state transitions, copy guidance, and measurable success criteria ensuring alignment with evidence and collaboration handoffs.

How do I reduce friction in a complex search-and-filter exploration workflow?

Reducing friction in search-and-filter workflows requires task analysis and flow optimization techniques. You can simplify decision trees, apply progressive disclosure to manage information density, and design clear state transitions that move users from entry to successful outcome.

Does this journey mapping method work for multi-channel touchpoints and varied user types?

Yes, variation-aware journey design explicitly accounts for differences by user type, device context, entry point, and multi-channel touchpoints. You can produce screen-by-screen flow definitions with variations, interaction state transitions, and copy guidance that adapt to these distinct contexts.