Journey Mapping logo

Journey Mapping

Community
Productfculty-aipm
journey-mapping

Use this skill when the user asks to "create a journey map", "user journey map", "map the user experience", "map the customer journey", "end-to-end user flow", "what does the user experience look like", "map the onboarding journey", or wants to visualize the full sequence of steps a user goes through to accomplish a goal — including touchpoints, emotions, and friction points.

Overview

PublisherProductfculty-aipm
RepositoryPM-Copilot-by-Product-Faculty
Skill namejourney-mapping
Stars
80
Forks
34
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the Journey Mapping AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/journey-mapping
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/journey-mapping .claude/skills/journey-mapping
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Journey Mapping in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Journey Mapping on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Journey Mapping is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Journey Mapping

You are creating a user journey map — a visual and narrative representation of the complete user experience from awareness to outcome. Journey maps surface friction, emotion, and opportunity that individual screens or features can miss.

Framework: Service design principles, Teresa Torres (continuous discovery touchpoints), JTBD (progress map across stages).

Step 1 — Load Context

Read memory/user-profile.md and context/product/personas.md to identify the primary persona for this journey. Understand: what product stage is the user in (pre-launch → need to map the ideal journey; existing product → need to map the current reality)?

Step 2 — Define the Journey Scope

Clarify:

  • Which persona? Primary user from the persona file, or a specific segment?
  • Which goal? What is the user trying to accomplish in this journey? (e.g., "onboard and activate", "complete their first core task", "renew their subscription")
  • Which scope? End-to-end from awareness, or a specific phase (e.g., just the onboarding journey)?
  • Current vs. ideal? Are we mapping what happens today (to find problems) or what should happen (to design for)?

Step 3 — Journey Phases

Identify the major phases of the journey. Adapt to the user's specific flow, but use these as a starting point:

Awareness: How does the user first learn about the product? Consideration: What research or comparison do they do before trying it? Activation: Their first experience — signup, onboarding, first use Core loop: Regular use — the repeating pattern of value delivery Expansion: Discovering new features or use cases Retention / Renewal: Decision to continue using or subscribe Advocacy / Referral: Sharing with others

For a specific feature journey (not the full product): adapt phases to the feature's flow.

Step 4 — Journey Map Rows

For each phase, fill in:

User actions: What does the user actually do? (Steps, clicks, inputs, decisions)

Touchpoints: Where does the user interact with the product/brand? (In-app, email, Slack, support, etc.)

Thoughts: What is the user thinking at this step? (Uncertainty, expectation, intent)

Emotions: What are they feeling? (Use a simple scale: Frustrated → Neutral → Satisfied → Delighted)

Friction points: What makes this step hard or confusing?

Opportunities: What could be improved here? What would delight them?

Metrics available: Is there data for this step? (Conversion rate, time spent, drop-off rate)

Step 5 — Emotion Arc

After completing the rows, draw the emotion arc:

  • Plot the emotional score (1 = frustrated, 5 = delighted) for each phase
  • Identify: where are the valleys (worst experiences)? Where are the peaks (delight moments)?
  • The valleys are your highest-priority improvement opportunities
  • The peaks are your strengths to protect and build messaging around

Step 6 — Opportunity Prioritization

For each friction point identified:

  • Which OST opportunity does it map to?
  • How many users are affected?
  • How severe is the friction?

Rank opportunities by: severity × affected users. This gives you a data-driven prioritization of where to invest.

Step 7 — Output

Produce:

  • Journey map table (phases × rows)
  • Emotion arc summary (which phases are highest friction)
  • Top 3 opportunities ranked by impact
  • One "moment of delight" to protect and amplify

Offer to save to a Notion page (if connected) or outputs/journey-map-[persona]-[goal]-[date].md.

Frequently asked questions

What does the Journey Mapping AI skill do?

Use this skill when the user asks to "create a journey map", "user journey map", "map the user experience", "map the customer journey", "end-to-end user flow", "what does the user experience look like", "map the onboarding journey", or wants to visualize the full sequence of steps a user goes through to accomplish a goal — including touchpoints, emotions, and friction points.

Why use Journey Mapping on TypingMind?

Because you install it once and use it with any model. Journey Mapping is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Journey Mapping in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/journey-mapping. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Journey Mapping?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Journey Mapping?

As many as you like. As long as a model supports skills, you can use Journey Mapping with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Journey Mapping AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇