customer-journey-map
by phurynThe customer-journey-map skill helps you create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. It fits UX Research, onboarding improvement, and experience analysis when you need a structured journey story from messy inputs.
This skill scores 78/100 and is a solid listing candidate. It gives directory users enough structure to install with confidence: a clear trigger, a defined customer-journey workflow, and concrete stage-by-stage guidance. It is not fully polished as a packaged skill, but it is operationally useful and should reduce guesswork versus a generic prompt.
- Clear trigger and use case: maps customer experience from awareness through advocacy, including onboarding, retention, and friction points.
- Strong workflow guidance: instructs the agent to define a specific persona and document stages, touchpoints, emotions, pain points, and opportunities.
- Good progressive disclosure: asks the agent to read provided files first and use web search when a URL is supplied, which improves applicability.
- No install command, support files, or external references, so users should expect a standalone prompt-style skill rather than a fully supported toolkit.
- The excerpt shows only partial documentation structure and no examples, so edge-case execution may still require some agent judgment.
Overview of customer-journey-map skill
What the customer-journey-map skill does
The customer-journey-map skill helps you create an end-to-end customer journey map with clear stages, touchpoints, emotions, pain points, and opportunities. It is best for UX Research, product teams, and marketers who need a structured view of how a person moves from awareness to advocacy, not just a list of features or complaints.
When this skill is the right fit
Use the customer-journey-map skill when you need to identify friction, improve onboarding, compare alternatives, or explain where the experience breaks down. It is especially useful when you have messy inputs such as interview notes, survey responses, support tickets, or analytics and want a coherent journey story instead of isolated observations.
What makes it different
This skill is opinionated about the journey structure: it expects a specific persona, stage-based mapping, and stage-by-stage analysis of what the user thinks, feels, and does. That makes the output more decision-ready than a generic prompt because it pushes you to define the job-to-be-done, not just describe product usage.
How to Use customer-journey-map skill
Install and start with the source file
Install the customer-journey-map skill with npx skills add phuryn/pm-skills --skill customer-journey-map. Then read SKILL.md first, because it contains the actual workflow and stage model. In this repository, there are no helper scripts or support folders, so the skill file is the primary source of truth.
Give the skill the right input
The strongest customer-journey-map usage starts with a specific persona and a concrete scenario. Good input looks like: “Map the journey for a first-time SaaS admin who is evaluating a trial after reading a comparison page,” or “Map the journey for a mobile shopper trying to reorder a product after a bad delivery experience.” Weak input like “make a customer journey map” forces the model to invent too much.
Read the output in the right order
The workflow in the skill is built around stages: awareness, consideration, acquisition, onboarding, engagement, retention, and advocacy. As you review the result, check whether each stage has realistic touchpoints, emotions, and pain points for the persona you gave it. If you have source material, validate the map against evidence before treating it as a strategy artifact.
Practical prompting tips
For better customer-journey-map usage, include any of these when available: product URL, target persona, funnel stage, known friction points, interview transcripts, support themes, or metrics you want explained. If you want a UX Research output, say so explicitly and ask the skill to emphasize observed behavior, quotes, or hypotheses tied to evidence. If you want a simpler map, limit the scope to one persona and one primary journey.
customer-journey-map skill FAQ
Is the customer-journey-map skill beginner friendly?
Yes, if you can describe the product and audience in plain language. The skill gives a clear stage framework, so beginners do not need to invent a research method from scratch. What matters most is providing enough context for a believable persona and journey.
How is this different from a normal prompt?
A normal prompt can produce a journey map, but the customer-journey-map skill is better when you want repeatable structure and fewer missing stages. It nudges the model to cover touchpoints, emotions, pain points, and opportunities instead of producing a high-level summary that looks complete but is hard to act on.
When should I not use it?
Do not use the customer-journey-map skill if you only need a short marketing persona, a feature list, or a one-screen UX critique. It is also a poor fit when you have no idea who the traveler is or no real product context, because the result will be too generic to trust.
How to Improve customer-journey-map skill
Make the persona and JTBD explicit
The biggest quality boost comes from specifying who the customer is and what they are trying to accomplish. Instead of “new user,” use “freelance designer trying to onboard a client in under 10 minutes.” That gives the customer-journey-map skill a concrete lens for stage behavior, friction, and emotion.
Feed evidence, not just opinion
If you have transcripts, tickets, surveys, or analytics, provide them and ask the skill to synthesize patterns rather than inventing details. The skill is strongest when it can ground pain points in real signals, especially for customer-journey-map for UX Research where credibility matters more than polish.
Refine after the first draft
Use the first output to spot missing stages, vague touchpoints, or pain points that are too generic. Then iterate by asking for one narrower persona, one journey variant, or a sharper outcome such as “focus on onboarding drop-off” or “highlight retention risks after the first purchase.” This usually improves customer-journey-map usage more than asking for a longer map.