← Back to list
⚡

customer-journey-map Checked

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and op…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
7.3Overall rating
2Views
5Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "customer-journey-map" skill by following the instructions at https://skill123.me/install/customer-journey-map.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/customer-journey-map.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 2 KB
📊 Static rating
7.3/10
Trigger
6.5
Structure
8.0
Workflow
6.8
Content
9.0
Engineering
3.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.

Documentation

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

### Context

You are creating a customer journey map for **$ARGUMENTS**.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

### Instructions

1. **Define the persona**: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

2. **Map the journey stages** (adapt to the product):

| Stage | Description |

|---|---|

| **Awareness** | How do they first learn about the product? |

| **Consideration** | What do they evaluate? What alternatives do they compare? |

| **Acquisition** | How do they sign up or purchase? |

| **Onboarding** | First experience with the product — time to value |

| **Engagement** | Regular usage — building habits |

| **Retention** | What keeps them coming back? What might cause churn? |

| **Advocacy** | When and why do they recommend the product to others? |

3. **For each stage, document**:

  • **Touchpoints**: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
  • **User actions**: What they do at this stage
  • **Thoughts & questions**: What's on their mind ("Is this worth my time?" "How do I...?")
  • **Emotions**: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
  • **Pain points**: Friction, confusion, drop-off risks
  • **Opportunities**: How to improve the experience at this point

4. **Identify critical moments**:

  • **Aha moment**: When the user first experiences core value
  • **Moments of truth**: Decision points where they commit or abandon
  • **Churn triggers**: Where users most commonly drop off

5. **Create the journey map table**:

| Stage | Touchpoint | User Action | Emotion | Pain Point | Opportunity |

|---|---|---|---|---|---|

6. **Recommend prioritized improvements**:

  • Which pain points have the highest impact on conversion or retention?
  • What quick wins can improve the experience immediately?
  • What requires deeper investment but has the biggest payoff?

Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.

---

### Further Reading

View full documentation

Score breakdown

Trigger
6.5
Good What and When with journey-mapping synonyms, but no When-Not exclusion for adjacent UX-research requests.
Structure
8.0
Compact 65-line single file with no scripts or references; appropriate size for a prompting skill.
Workflow
6.8
Task-oriented steps with JTBD persona, aha/churn moment analysis, and output table, but verification is only a weak think-step-by-step nudge.
Content
9.0
Crisp imperative instructions with ready-to-fill table scaffolds and concrete examples.
Engineering
3.0
Valid frontmatter; external links to a credible PM site; no local path references.
Security
9.5
No scripts, no injection, no secrets; external links are credible product blog articles.
Clear six-step journey mapping workflow with persona, stage table, and prioritized recommendations, but no verification loop and no When-Not boundary.