← Browse

@owl-listener/journey-map

A

Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.

skillclaude

Install

agr install @owl-listener/journey-map --target claude

Writes 1 file into .claude/skills/, pinned to git-b2cf334a.

  • .claude/skills/journey-map/SKILL.md

Document


name: journey-map description: Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.

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

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-b2cf334aa6012026-07-31