skills.rest
Mozurok
MozurokCOMMUNITY
Explore all skills by this author →
GitHub

journey-map

Document multi-screen user journeys into structured journey spec markdown files.

6|Updated Jul 10, 2026
Search Tags:#accessibility#user journey#product discovery#ux research#screen flow#journey map#spec documentation
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill journey-map-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: journey-map
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/journey-map
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill journey-map-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mapping a user flow across multiple screens is scattered work: screen specs live in separate docs, edge cases get missed, and accessibility or security concerns surface too late. This Skill consolidates screen references and a user story into one journey spec doc covering flow, states, and cross-cutting concerns. ## Core Features & Use Cases - Journey Spec Generation: Produces a JOURNEY_SPEC.md-compliant document with 11 sections covering outcome, screen flow, components, critical states, accessibility, security, and performance. - Flow Diagramming: Draws an ASCII journey map with screens as nodes, decision points as diamonds, and happy plus alternate paths. - Critical State Coverage: Documents at least four states (happy path, network error, validation failure, timeout) with triggers and UI responses. - Use Case: A product manager needs to spec a checkout flow spanning five screens. Provide the user story and screen doc references, and receive a complete journey doc saved to docs/research/journeys/ with open questions flagged for stakeholders. ## Quick Start Document the checkout user journey using the screen specs for cart, shipping, payment, and confirmation, and save it as a journey spec doc.

Frequently Asked Questions about journey-map

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

FAQPage Schema
How do I document a user journey across multiple screens?▼

Provide the journey name, persona, user story, and the list of screen docs involved. The Skill sequences the screens, draws an ASCII flow diagram with decision points, and writes an 11-section journey spec to docs/research/journeys/<journey-slug>.md.

What inputs does a journey mapping workflow need?▼

It requires a journey name and slug, the personas taking the journey, a user story or flow description, the list of screen docs or screen numbers involved, and the project workspace path.

When should I use journey mapping instead of a screen spec?▼

Use journey mapping when documenting a flow that traverses multiple screens. For a single screen use a screen-spec skill, and for a reusable UI pattern use a pattern-doc skill instead.

What critical states does a journey spec cover?▼

The spec documents at least four states: happy path, network error, validation failure, and timeout or slow response. Each entry records the state name, trigger, UI response, and affected screens.

Does the journey spec cover accessibility and security?▼

Yes. It documents VoiceOver/TalkBack flow, focus order, screen announcements, and Reduced Motion behavior, plus FLAG_SECURE screens, cache purging on exit, idle lock behavior, and screenshot restrictions.

Related Skills

Explore More Product & Management Skills→
rladydqls99rladydqls99

screen-analysis

Analyze planning documents to derive screens and component structures.

Community
Intermediate
AgentiveStackAgentiveStack
71

slice

Break a plan into end-to-end vertical slices covering schema, backend, API, UI, and tests.

Official
Intermediate
diegosanchespereira1diegosanchespereira1

bmad-market-research

Turn market questions into verified research reports with citations.

Community
Advanced
nevesbnevesb

ux-design

Generate markdown UX specifications for game screens, HUDs, and interaction patterns.

Community
Advanced