journey-mapping

journey-mapping is a skill for Claude Code, Codex from rampstackco/claude-skills. It costs 131 tokens per session (2,143 once invoked), scanned A, original, MIT.

A method for mapping the full experience a customer has with a product or service. It records steps, contact points, feelings, problems, and the behind-the-scenes systems involved.

In plain words
What is it for?
Use it to map a user segment's journey, diagnose friction across touchpoints, plan a new product or feature in context, and align teams on front-stage and back-stage work.
Why use it?
It helps teams see where an experience becomes confusing or disconnected instead of each department viewing only its own part. The shared map can reveal where users struggle or stop progressing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Part of the rampstack-skills plugin — 103 skills shipped together

Good fit Use it to map a user segment's journey, diagnose friction across touchpoints, plan a new product or feature in context, and align teams on front-stage and back-stage work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rampstackco/claude-skills/journey-mapping
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add rampstackco/claude-skills --skill journey-mapping
Clone the repo
git clone --depth 1 https://github.com/rampstackco/claude-skills

Made for: Claude Code, Codex.

Or install rampstack-skills, the plugin that ships this one along with the rest of its 103 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for journey-mapping

README.md
[![agentmods](https://agentmods.dev/badge/skills/rampstackco/claude-skills/journey-mapping.svg)](https://agentmods.dev/skills/rampstackco/claude-skills/journey-mapping)
Your own site
<a href="https://agentmods.dev/skills/rampstackco/claude-skills/journey-mapping"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/journey-mapping.svg" alt="Measured on agentmods" height="20"></a>
Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,143 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00131 $0.02143
Opus 5 $0.00066 $0.01071
Sonnet 5 $0.00026 $0.00429
Haiku 4.5 $0.00013 $0.00214

Measured 8d ago against content hash 5d25b07dd3c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

journey-mapping scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/journey-mapping/SKILL.md · 251 lines

How it starts

The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Journey Mapping

Build journey maps and service blueprints that surface friction, align teams, and identify opportunities. Stack-agnostic. Tool-agnostic.

This skill is for mapping the experience. For testing specific touchpoints, use usability-testing. For broader generative research, use ux-research. For analyzing conversion, use cro-optimization.


When to use

  • Departments have different mental models of the customer experience
  • Customer experience feels disjointed across touchpoints
  • Specific friction or drop-off points need diagnosis
  • Strategic planning needs a shared view of the user
  • Service design (front-stage and back-stage) needs alignment
  • New product or feature needs to be designed in context of broader experience

When NOT to use

  • Testing a single touchpoint or page (use usability-testing)
  • Generative research before journey mapping (use ux-research)
  • Operational process mapping that doesn't involve users
  • Funnel optimization (use cro-optimization)

Required inputs

  • Identified user persona or segment to map (one map per segment)
  • Existing research and data about that segment
  • Cross-functional access (you cannot map back-stage without ops/support/engineering input)
  • Time and stakeholder commitment (a real journey map is a project, not an afternoon)

The framework: 3 deliverables

1. Customer journey map

The user-facing view of the experience.

Structure (rows / lanes):

  • Phase. The major stages in the journey (e.g., Awareness, Consideration, Onboarding, Activation, Retention, Advocacy). Phases vary by product type.
  • Steps. Specific things the user does within each phase.
  • Touchpoints. Where the user interacts with the product, brand, or service (web, app, email, support, social, in-person).
  • Goals. What the user is trying to accomplish at this step.
  • Thoughts. What's going through their mind.
  • Emotions. The emotional state (often visualized on a curve).
  • Pain points. Where things go wrong, friction, frustration.
  • Opportunities. Where the experience could improve.

Read the full file on GitHub · 251 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 251 lines · 131 tokens per session scan A 5d25b07dd3c6

Subscribe to this mod's changes

journey-mapping is a skill published in the GitHub repository rampstackco/claude-skills (830 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 2,143 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

popular-web-designs

54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.

NousResearch/hermes-agent · 23 tokens

visual-qa

Runs rigorous visual QA across web, terminal, and paginated surfaces with screenshot evidence and a verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right.

code-yeongyu/oh-my-openagent · 47 tokens

frontend

Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.

code-yeongyu/oh-my-openagent · 49 tokens

interaction-skill

Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…

code-yeongyu/oh-my-openagent · 104 tokens

layout-skill

Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…

code-yeongyu/oh-my-openagent · 88 tokens

johnny-suede-design

Suede Labs AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to…

JasonColapietro/suede-creator-skills · 179 tokens