customer-journey-map · deanpeters — Claude Code skill: map the customer path

What customer-journey-map does

The skill walks through steps: it first asks for a persona and a scenario, then lays out the journey stage by stage, from first contact with the brand to repeat purchases. Each stage records what the customer does, where they interact, how they feel, plus KPIs, business goals and the teams that own the stage. The result is a working artifact for diagnosis and prioritisation, not a user flow diagram.

A template.md file holds the full fill-in structure, and the work is split into steps: prepare the inputs, set objectives, pick one persona, fill in the stages. Persona and scenario come first — without a specific actor and goal the map turns into a generic funnel. If you already passed context in the invocation, the skill skips those questions.

You need personas, a list of stages and an inventory of touchpoints before you start. If any of that is missing, run discovery interviews, persona definition or a touchpoint audit first — otherwise there is nothing to fill in. For deep product-specific workflows a story map fits better.