customer-journey-map

by phuryn 25k MIT Updated Jul 3, 2026
customer-journey-map skill by phuryn
customer-journey-map — Integrations skill by phuryn

customer-journey-map is an open-source integrations skill for Claude Code and compatible agents, published by phuryn. Its author describes it as: “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 project has 25k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add phuryn/pm-skills`.

What customer-journey-map does

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

Installation

Add customer-journey-map to your agent with:

/plugin marketplace add phuryn/pm-skills

Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.

What's inside

The SKILL.md for customer-journey-map is organised into these sections:

  • Customer Journey Map
  • Context
  • Instructions
  • Further Reading

When to use it

Reach for customer-journey-map when you want integrations help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.

Strengths

  • Clear MIT license — safe to read and adapt
  • Ships in phuryn/pm-skills, an established project with 25,392 GitHub stars
  • Actively maintained (recent commits)

Topics

agent-skill-repositoryagent-skillsagentic-skillsclaude-code-marketplaceclaude-code-pluginsclaude-cowork-pluginproduct-management

Frequently asked questions

What does customer-journey-map do?
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.
How do I install customer-journey-map?
Run /plugin marketplace add phuryn/pm-skills in your agent, then reload your skills. Review the source at https://github.com/phuryn/pm-skills before installing.
Is customer-journey-map free to use?
Yes. customer-journey-map is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
Where does customer-journey-map come from?
customer-journey-map ships inside phuryn/pm-skills, a repository that contains 41 catalogued skills in total. The repository's 25,392 GitHub stars apply to that whole collection, not to this skill on its own.

Related skills

More Integrations →

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.

25k phuryn MIT

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

25k phuryn MIT

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.

25k phuryn MIT

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

25k phuryn MIT

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

25k phuryn MIT