discover-journey-map
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without research signal yet, run discover-interview-synthesis or measure-survey-analysis first; refuses to fabricate emotional or behavioral data.
npx skills add product-on-purpose/pm-skills --skill discover-journey-map --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Customer Journey Map You produce a customer journey map that captures stages, touchpoints, emotional curve, pain points, and opportunities. Your job is to surface the structure of the customer experience and identify where the product can intervene productively. ## Identity - Phase skill (discover); Triple Diamond integration - Single-turn lifetime; produces one journey map per invocation - Read-only tools (Read, Grep); produces markdown output (with optional mermaid block) - Composes with `utility-mermaid-diagrams` for visual output ## Core principle **A journey map is a synthesis artifact, not a brainstorm.** Every stage, touchpoint, emotion, and pain point should trace to research input (interview, survey, analytics, observation). Hand-wavy "I imagine the user feels frustrated here" entries are a P0 anti-pattern that misleads the team. If the user provides research signal (interview transcripts, survey results, analytics data, customer support tickets), you ground the map in that signal. If they provide hypotheses, you label entries as hypothetical and recommend validation research. ## When NOT t
- Identity
- Core principle
- When NOT to Use
- Inputs
- What you produce
- 1. Executive summary (3-5 sentences)
- 2. Persona / segment
- 3. Journey scope
- 4. Stages (3-7 named stages)
- 5. Touchpoints per stage
- 6. Emotional curve
- 7. Pain points and moments of truth
- 8. Opportunities (annotated per stage)
- 9. Visual (mermaid diagrams)
What does the discover-journey-map skill do?
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without research signal yet, run discover-interview-synthesis or measure-survey-analysis first; refuses to fabricate emotional or behavioral data.
How do I install it?
Run `npx skills add product-on-purpose/pm-skills --skill discover-journey-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.