journey-map
Journey-map is a Claude Code skill that creates detailed user journey maps across 5-7 stages, documenting goals, actions, touchpoints, emotions, and pain points for a specific persona and scenario. Use this skill when analyzing the complete user experience for a product, feature, or service to identify friction points, emotional highs and lows, and prioritized design opportunities.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/journey-map && cp -r /tmp/journey-map/design-research/skills/journey-map ~/.claude/skills/journey-mapSKILL.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.
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 GarrettFacilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
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`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.