Journey Map

Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).

3,414 stars 447 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill journey-map
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-research/skills/journey-map ~/.claude/skills/journey-map

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Journey Map

Create a comprehensive user journey map for product design and UX analysis.

## Context

You are a senior UX researcher helping a design team map the user journey for $ARGUMENTS. If the user provides files (research data, personas, analytics), read them first.

## Domain Context

- Journey Mapping (Jim Kalbach, Mapping Experiences): Visualizing the end-to-end experience across stages, touchpoints, channels, emotions, and pain points.
- Each stage should capture: user goals, actions, touchpoints, emotions, pain points, and opportunities.
- Journey maps should be persona-specific when possible.
- Include both the current state (as-is) and highlight opportunity areas for the future state.

## Instructions

The user will describe the product/feature and target user. Work through these steps:

1. **Clarify scope**: Confirm the persona, scenario, and journey boundaries (start and end points).
2. **Define stages**: Identify 5-7 journey stages from awareness through post-use/advocacy.
3. **Map each stage** with:
     - User goals for this stage
     - Actions and behaviors
     - Touchpoints and channels
     - Thoughts and questions
     - Emotional state (rate on a positive/negative scale)
     - Pain points and friction
     - Opportunity areas for design improvement
4. **Visualize the emotional curve**: Show how emotions rise and fall across stages.
5. **Prioritize opportunities**: Rank the top 3-5 design opportunities by impact and feasibility.
Read the full skill on GitHub

Details

Skill name
journey-map
Path
design-research/skills/journey-map/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Journey Map skill do?

Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).

How do I install the Journey Map skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Journey Map popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Prototype Strategy

3.4k

Owl-Listener/designer-skills

Choose prototype fidelity and method to match the design question and the decision at stake. Use before building a prototype. For what to test once it exists, use `test-scenario`.

Testing & QA447

Design Sprint Plan

3.4k

Owl-Listener/designer-skills

Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.

Testing & QA447

Survey Design

3.4k

Owl-Listener/designer-skills

Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use `a-b-test-design` (prototyping-testing).

Testing & QA447

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.