agentleFS
yuusakuriyuusakuri/agent-skills/skills/customer-journey-map/SKILL.md

customer-journey-map

Skill2 starsChanged 10 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first.

    line 14
  2. Distinctive:

    Aha moment: When the user first experiences core value

    line 42

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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):

    StageDescription
    AwarenessHow do they first learn about the product?
    ConsiderationWhat do they evaluate? What alternatives do they compare?
    AcquisitionHow do they sign up or purchase?
    OnboardingFirst experience with the product — time to value
    EngagementRegular usage — building habits
    RetentionWhat keeps them coming back? What might cause churn?
    AdvocacyWhen 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:

    StageTouchpointUser ActionEmotionPain PointOpportunity
  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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.