.claude/skills/customer-journey-map/SKILL.md
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.
npx skillsauth add omeragaakbas/zoyare customer-journey-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.
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.
Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.
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? |
For each stage, document:
Identify critical moments:
Create the journey map table:
| Stage | Touchpoint | User Action | Emotion | Pain Point | Opportunity | |---|---|---|---|---|---|
Recommend prioritized improvements:
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.
development
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
data-ai
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
development
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
documentation
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.