User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points.
Install Journey Map
$ npx skills add Owl-Listener/designer-skills --skill journey-map -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills journey-map --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-research/skills/journey-map .claude/skills/journey-map && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "journey-map" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-map into .claude/skills/journey-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-map", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-mapType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill journey-map -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills journey-map --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-research/skills/journey-map .agents/skills/journey-map && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "journey-map" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-map into .agents/skills/journey-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-map", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill journey-map -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills journey-map --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-research/skills/journey-map .cursor/skills/journey-map && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "journey-map" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-map into .cursor/skills/journey-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-map", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path design-research/skills/journey-map--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill journey-map -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills journey-map --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-research/skills/journey-map .gemini/skills/journey-map && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "journey-map" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-map into .gemini/skills/journey-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-map", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills journey-mapInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill journey-map -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-research/skills/journey-map .github/skills/journey-map && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "journey-map" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-map into .github/skills/journey-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-map", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill journey-map -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills journey-map --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-research/skills/journey-map .opencode/skills/journey-map && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "journey-map" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/journey-map into .opencode/skills/journey-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-map", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
journey-map- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~518 tokens
- SKILL.md length
- 237 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points.
- Works in 7 steps: Clarify scope: Confirm the persona,… → Define stages: Identify 5-7 journey… → Map each stage with → …
- Improving an existing experience
- SKILL.md covers Context, Domain Context, Instructions and Further Reading
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Journey Map is an agent skill from Owl-Listener/designer-skills. Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use experience-map (ux-strategy); for screen-level paths use user-flow-diagram (prototyping-testing).
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Customer journey mapping. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Improving an existing experience
- Tasks that involve Customer journey mapping
Example prompts
- “/journey-map”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Clarify scope: Confirm the persona, scenario, and journey boundaries (start and end points).
- Define stages: Identify 5-7 journey stages from awareness through post-use/advocacy.
- Map each stage with
- Visualize the emotional curve: Show how emotions rise and fall across stages.
- Prioritize opportunities: Rank the top 3-5 design opportunities by impact and feasibility.
- Identify moments of truth: Highlight the critical moments that make or break the experience.
- Think step by step. Present in a clear, structured format.
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Journey Map loads about 518 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 237 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 237 words, ~518 tokens.
Download SKILL.mdSave it as
.claude/skills/journey-map/SKILL.md (or your agent's skills folder).- name
- journey-map
- description
- Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).
Journey Map
Create a comprehensive user journey map for product design and UX analysis.
Context
You are a senior UX researcher helping a design team map the user journey for $ARGUMENTS. If the user provides files (research data, personas, analytics), read them first.
Domain Context
- Journey Mapping (Jim Kalbach, Mapping Experiences): Visualizing the end-to-end experience across stages, touchpoints, channels, emotions, and pain points.
- Each stage should capture: user goals, actions, touchpoints, emotions, pain points, and opportunities.
- Journey maps should be persona-specific when possible.
- Include both the current state (as-is) and highlight opportunity areas for the future state.
Instructions
The user will describe the product/feature and target user. Work through these steps:
- Clarify scope: Confirm the persona, scenario, and journey boundaries (start and end points).
- Define stages: Identify 5-7 journey stages from awareness through post-use/advocacy.
- Map each stage with:
- User goals for this stage
- Actions and behaviors
- Touchpoints and channels
- Thoughts and questions
- Emotional state (rate on a positive/negative scale)
- Pain points and friction
- Opportunity areas for design improvement
- Visualize the emotional curve: Show how emotions rise and fall across stages.
- Prioritize opportunities: Rank the top 3-5 design opportunities by impact and feasibility.
- Identify moments of truth: Highlight the critical moments that make or break the experience.
- Think step by step. Present in a clear, structured format.
Further Reading
- Mapping Experiences — Jim Kalbach
- The Elements of User Experience — Jesse James Garrett
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in design-research/skills/journey-map of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Journey Map next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Journey Map this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~518 | Automated safety check: Pass | MIT | |
| User Story Mappingdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| QA Critical UXfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Prdjuanandresgs/claude-ctrl | 193 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Journey Map Builderdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~3.7k | Automated safety check: Pass | Custom licence | |
| Super Product Ownersyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~7.9k | Automated safety check: Pass | None |
Similar skills
QA Critical UX
fastrepl/anarlog
QA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.
Prd
juanandresgs/claude-ctrl
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.
Customer Journey Map Builder
deanpeters/Product-Manager-Skills
Builds a stage-by-stage customer journey map covering actions, touchpoints, emotions, KPIs, goals, and owning teams for one persona and scenario.
Super Product Owner
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…
Attribution Analysis Modeling
liangdabiao/claude-data-analysis-ultra-main
Perform multi-touch attribution analysis using Markov chains, Shapley values, and custom attribution models.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Journey Map
What does Journey Map do?
Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Journey Map is an agent skill from Owl-Listener/designer-skills. Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points.
When should I use Journey Map?
Journey Map fits situations like: improving an existing experience; tasks that involve Customer journey mapping.
How do I install Journey Map in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill journey-map -a claude-code`. Or copy the skill folder (design-research/skills/journey-map in Owl-Listener/designer-skills) into .claude/skills/journey-map in your project. Claude Code loads it when a task matches its description.
How do I install Journey Map in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill journey-map -a codex`. Or copy the skill folder (design-research/skills/journey-map in Owl-Listener/designer-skills) into .agents/skills/journey-map in your project. Codex loads it when a task matches its description.
Can I use Journey Map in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill journey-map -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/journey-map, .gemini/skills/journey-map, .github/skills/journey-map and .opencode/skills/journey-map in your project.
What does Journey Map need to run?
SKILL.md names no scripts, command-line tools or credentials: Journey Map is instructions for the agent only.
Does Journey Map access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Journey Map safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Journey Map use?
Journey Map is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Journey Map use?
About 518 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Journey Map?
Skills that share tags, products or a category with Journey Map: User Story Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), QA Critical UX (fastrepl/anarlog, 9.5k stars), Prd (juanandresgs/claude-ctrl, 193 stars) and Customer Journey Map Builder (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Journey Map?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.