journey

Design end-to-end user journeys across mobile, web, and embedded channels.

116|9|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ghaida/intent --skill journey-ghaida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/ghaida/intent/tree/main/skills/journey
Command: npx skills add https://github.com/ghaida/intent --skill journey-ghaida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design end-to-end user journeys that span sequences of screens, states, and interactions across platforms to ensure coherent experiences and reduce drop-off.

Core Features & Use Cases

  • End-to-end flow mapping across mobile, web, and embedded contexts.
  • Variation handling by user type, device, and entry point.
  • Cross-channel journey design and state management for save/resume and handoffs.

Quick Start

Map a complete signup journey from entry to completion, including error handling and cross-channel touchpoints.

Frequently Asked Questions about journey

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

FAQPage Schema
How do I design end-to-end user journeys across multiple channels?

Design end-to-end user journeys by mapping complete sequences of screens, states, and interactions across mobile, web, and embedded contexts. This approach ensures coherent cross-channel experiences and reduces user drop-off during task completion.

What is cross-channel continuity in journey design?

Cross-channel continuity in journey design ensures seamless transitions for users moving between mobile, web, and embedded contexts. It manages save and resume states, enabling users to complete tasks without losing progress across different devices and touchpoints.

How do I handle user journey variations based on device or entry point?

Handle user journey variations by specifying different flow paths based on user type, device, and entry point. This ensures the mapped journey adapts to distinct contexts, providing optimized experiences for each interaction scenario.

Can I map a complete onboarding flow from entry to completion?

You can map a complete onboarding flow from initial entry to final completion, including specific error handling and cross-channel touchpoints. This ensures every state and interaction is accounted for in the signup journey.

What's the best way to manage journey states for design handoff?

Manage journey states for handoff by generating journey-state management artifacts that document end-to-end flow mapping. These artifacts specify cross-channel continuity and variation handling, ensuring developers understand save and resume logic.

Does this approach work for designing checkout funnels and notification sequences?

This approach works for designing checkout funnels, notification sequences, dashboards, and multi-device journeys. It maps end-to-end interactions across mobile and web contexts to optimize task completion rates.