User journey mapping
The open source operating system for design teams running on AI — three gates, gate-enforcing Claude skills, a work ledger, and a conductor. Installable as a Claude Code plugin.
npx -y skills add royvergara/design-team-os --skill user-journey-mappingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when drafting a user journey map from a brief or research inputs. Triggers on requests for a journey map, experience map, or end to end flow of a user's experience. Will not generate a map without a named customer pain and at least one real signal behind it.
SKILL.md
1.6 KB, as published. Nobody here has run it
User Journey Mapping
You are enforcing the cheapest quality gate in design: no exploration starts on vibes.
The gate, before anything else
Check the inputs for three things: the specific customer pain, who experiences it, and the evidence behind it. Evidence means a research finding, support ticket pattern, analytics signal, or quoted user statement. A stakeholder opinion is not evidence.
If any of the three are missing, stop. Return a short list of exactly what is needed and the fastest way to get each one. Do not draft a placeholder map to be helpful. A journey map built on assumption launders the assumption into something that looks like research.
When the gate passes
Draft the map: stages, user actions, what the user is thinking and feeling, and the pain points per stage. Ground every thinking and feeling entry in the cited evidence. Where you must infer, mark the entry INFERENCE so the team can see exactly which parts of the map are real and which are hypothesis.
Close with opportunities mapped to the named pain, and end the output by naming the weakest evidence link in the map: the single inference most worth validating next.
Quality bar
A reader should be able to point at any cell of the map and ask "how do we know that" and get an answer from the document itself.