agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/customer-journey-map/SKILL.md

customer-journey-map

Skill1 starsChanged 24 days agoMITView on GitHub

Maps the end-to-end customer journey when acquisition, conversion, onboarding or retention problems need a customer's-eye view.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-okrs, outcome-roadmap and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 5 projects that use this

  • skytiger6724Skill

    outcome-roadmap

    Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

    Also in 5 projects that use this

  • miovragSkill

    strategy-red-team

    Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

    Also in 4 projects that use this

  • 45ckSkill

    porters-five-forces

    Also in 6 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 5 projects that use this

  • +6 more from skytiger6724

The file

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

    Use when conversion or retention is weak without a clear cause, before redesigning onboarding or service, or when teams disagree about what …

    line 9
  2. Distinctive:

    Every pain point has an owner

    line 31

“Common” is measured: kept by at least 6 in 10 of the 18 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

When to use it

Use when conversion or retention is weak without a clear cause, before redesigning onboarding or service, or when teams disagree about what customers experience.

What Claude needs

  • client-context.md for business background
  • Target customer segment
  • Funnel and retention data by stage
  • Customer interviews, reviews, support tickets or survey results
  • Touchpoints and the teams that own them

Method

  1. Define the segment and the journey's start and end points.
  2. List stages from first awareness to renewal or referral, with the customer's goal at each stage.
  3. Record touchpoints, the owning team, and evidence of what customers do and feel at each stage.
  4. Mark drop-off and pain points from data, labelling anything without evidence as a hypothesis.
  5. Identify the moments that most affect conversion or loyalty, and the internal causes behind failures.
  6. Prioritise improvements by impact, effort and owner.

Output format

Provide a journey map table (stage, customer goal, touchpoints, owner, evidence, pain points, metric), the five moments that matter most, and a prioritised improvement list.

Quality checks

  • Built from customer evidence, not internal assumptions alone
  • Every pain point has an owner
  • Each proposed fix has a metric to measure it

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.

Check your setup, free