# User Journey Mapper

> Use this when a feature or product needs a clear end-to-end user journey across entry, action, system response, and outcome. Trigger on requests to map the full experience before screens or components are finalized.

- Skill: `saranskumar/user-journey-mapper` (Agent Skill)
- Install (CLI): `npx skillmds@latest add saranskumar/user-journey-mapper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saranskumar/user-journey-mapper/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: saranskumar (https://skillmd.com/u/saranskumar)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/saranskumar/user-journey-mapper

---


# Goal
Map the user journey in a way that directly informs implementation and UX structure.

# When to Use
- The journey spans several states or surfaces.
- The team needs to understand user movement before screen design.
- UX work needs clearer context around goals and friction points.

# Instructions
1. Define the user, trigger, goal, and desired outcome.
2. Map the happy path first.
3. Add branch points for failure, waiting, permissions, and return paths.
4. Note where backend or async events change the experience.

# Constraints
- Keep the map tied to a real task.
- Do not turn the journey into generic product theory.
- Make implementation-relevant states explicit.

# Output Format
- user and goal
- journey steps
- branch and failure points
- implementation notes

# Examples
- "Map the journey for inviting a teammate and getting first value."
- "Show the user path through this report workflow."