journey-map
Skill2 starsChanged 50 days agoMITView on GitHub
Build a journey map for a persona from her Product usage moments and linked Pains/Signals. Use when the user runs /journey-map, asks for a customer/user journey, or a designer wants pain points mapped to moments of use.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- 45ck/hci-review-skilltheir own version, first seen Nov 11, 2026
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 2026
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- coco-research/cocotheir own version, first seen Nov 1, 2026
- Mozurok/fhorja.devtheir own version, first seen Oct 8, 2026
- cabbagecachekid/neon-jetpacktheir own version, first seen Aug 19, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- coco-research/coco★ 797same name
- launchapp-dev/animus-cli★ 39same name
- 45ck/hci-review-skill★ 19same name
- lalulali/vespyr★ 11same name
- Mozurok/fhorja.dev★ 10same name
- miguelclavel/ux-research-skills★ 1same name
- miovrag/claude-skills★ 1same name
- cabbagecachekid/neon-jetpack★ 0same name
- nbirkner/digital-brain★ 0same name
- talgacapri/pm-os★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- affinitySkill
- ai-personaSkill
- analytics-syncSkill
- backlogSkill
- catalogSkill
- cold-startSkill
- contradictionsSkill
- demo-dataSkill
- dovetail-syncSkill
- exportSkill
- extract-findingsSkill
- feature-panelSkill
- forget-participantSkill
- graph-lintSkill
- interview-guideSkill
- opportunity-treeSkill
- persona-avatarSkill
- persona-querySkill
- persona-talkSkill
- persona-voiceSkill
- persona-workshopSkill
- prdSkill
- prioritizeSkill
- researcherSkill
- retentionSkill
- source-syncSkill
- subject-accessSkill
- welcomeSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read the persona + her linked Signals/Evidence (+ Product Context.md for feature names the map may reference descriptively).
- Very specific: line 33
Keep the map per-persona. A cross-persona map is really a comparison — point to /persona-talk --panel findings or build one map per persona …
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
journey-map — Journey map from the graph
Generate a journey map where every pain point is a citation, not an opinion. The stages come from the persona's actual Product usage moments; the pains at each stage come from her linked Signals/Evidence — clickable back to source.
Trigger
/journey-map Personas/Emma.md
/journey-map Personas/Emma.md --scenario "commute" ← one scenario, deeperWorkflow
- Read the persona + her linked Signals/Evidence (+
Product Context.mdfor feature names the map may reference descriptively). - Derive stages from data: the "When she listens / uses" moments in
Product usage(e.g. morning commute → workday background → gym) — never a generic Awareness→Retention template. If the data only supports two stages, the map has two stages. - For each stage fill:
- Doing — observed behaviour (Product usage, Signals)
- Thinking/feeling — only from quotes and Signal observations; no invented inner monologue
- Pain points — each one linked to its Signal/Evidence file, with its Level (analyst artefact — codes allowed) and a staleness note where the 3-month rule applies
- Opportunities — only from existing
## Correlations→ Opportunity:lines andIdeas/files, named and linked
- Gaps stay visible: a stage with no researched pain gets an explicit "no data — not researched" cell, not a plausible guess. Offer to add those gaps to
Research backlog.md. - Output as a markdown table (default) — offer to save as
Research/Journey <Persona> <YYYY-MM-DD>.md, and optionally a Mermaidjourneydiagram for quick pasting into docs.
Rules
- Nothing enters the map that isn't in the graph — a journey map is a view of the data, not new synthesis. New hypotheses it provokes go to the backlog.
- Emotions shown must trace to a quote or observation ("laughs at her own chaos" — INT-01 observer note), never inferred from stage logic ("users feel frustrated at checkout").
- Keep the map per-persona. A cross-persona map is really a comparison — point to
/persona-talk --panelfindings or build one map per persona side by side.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

