journey-map — Claude Code skill: map a user's end-to-end journey
This skill maps one persona's end-to-end experience: stages, touchpoints, emotions and pain points. Useful when you're improving something that already exists.
npx skills add Owl-Listener/designer-skills --skill journey-map -a claude-codeWhat journey-map does
The skill walks the agent through a fixed sequence. It confirms the persona, scenario and journey boundaries, then splits the experience into 5–7 stages from awareness through post-use. Each stage gets user goals, actions, touchpoints and channels, thoughts and questions, an emotional rating, pain points and opportunity areas.
From there the agent draws the emotional curve across stages, ranks the top 3–5 design opportunities by impact and feasibility, and calls out the moments of truth. Hand it research files, personas or analytics and it reads them before starting — skip that and the map stays generic.
It is not a stand-in for its neighbours: for a multi-channel ecosystem use experience-map from ux-strategy, and for screen-level paths use user-flow-diagram from prototyping-testing. This one stays on a single persona and their whole journey.
What it helps with
- break an existing experience into stages and touchpoints
- spot where the emotional curve drops and why
- collect pain points and opportunity areas in one list
- flag the moments of truth that decide the experience
- rank design opportunities by impact and feasibility
Example prompts for the agent
- Build a journey map for the warehouse manager persona, scenario: first week in the new interface
- Map the journey from these interview notes, stages from awareness to repeat use
- Show the emotional curve and call out the moments of truth in this scenario
How to install journey-map
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill journey-map -a claude-code2Manually: put the files in place
~/.claude/skills/journey-map/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/journey-map/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill journey-map -a codex2Manually: put the files in place
.agents/skills/journey-map/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill journey-map -a cursor2Manually: put the files in place
.cursor/skills/journey-map/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills journey-map2Manually: put the files in place
.github/skills/journey-map/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill journey-map -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path design-research/skills/journey-mapManually: put the files in place
.devin/skills/journey-map/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill journey-map -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about journey-map
How do I install journey-map in Claude?
Run npx skills add Owl-Listener/designer-skills --skill journey-map -a claude-code. The skill lands in ~/.claude/skills/journey-map/SKILL.md.
What does journey-map do?
It maps one persona's journey: stages, goals, actions, touchpoints, emotions, pain points and opportunities. You get an emotional curve and a ranked list of improvements.
How is journey-map different from experience-map and user-flow-diagram?
journey-map covers one persona's experience. For a multi-channel ecosystem use experience-map from ux-strategy; for screen-level paths use user-flow-diagram from prototyping-testing.
Source text
SKILL.md · MIT
---
name: journey-map
description: 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).
---
# 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.
6. **Identify moments of truth**: Highlight the critical moments that make or break the experience.
7. Think step by step. Present in a clear, structured format.
## Further Reading
- Mapping Experiences — Jim Kalbach
- The Elements of User Experience — Jesse James Garrett
© Owl-Listener · MIT · Owl-Listener/designer-skills
