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).
npx skills add Owl-Listener/designer-skills --skill journey-map --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 a
- Context
- Domain Context
- Instructions
- Further Reading
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 it?
Run `npx skills add Owl-Listener/designer-skills --skill journey-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.