User Journey Mapper
Goal
Create visual user journey maps that document how users flow through your application to accomplish their goals. Ideal for UX design, workflow documentation, and understanding user experience before or after implementation.
Input
- Feature description - What the feature does
- User goal - What users want to accomplish
- Entry point - Where users start (homepage, email link, etc.)
Output
- Format: Markdown (
.md) with Mermaid diagrams
- Location:
docs/journeys/
- Filename:
[feature-name]-journey.md
Process
Phase 1: Context Gathering
Ask Journey Questions
I'll help map the user journey for [feature name].
Questions:
1. Where does the user start? (homepage, email, notification, etc.)
2. What is their end goal? (complete purchase, send message, etc.)
3. Are there different paths to the same goal?
4. What are common distractions or exit points?
5. Any existing user flow diagrams or wireframes?
Identify Journey Stages
Map the typical journey stages:
- Awareness: How do users discover this feature?
- Entry: Where do they enter the flow?
- Engagement: What actions do they take?
- Conversion: What's the success action?
- Exit: How do they leave (success, abandon, error)?
Phase 2: Map Primary Journey
Document Happy Path
Map the ideal, successful user journey:
## Primary Journey: [Goal Name]
**User Goal:** [What user wants to accomplish]
**Entry Point:** [Where they start]
**Success Outcome:** [What success looks like]
### Journey Steps
1. **[Stage 1 Name]** - [Page/Screen Name]
- **User Action:** [What user does]
- **System Response:** [What happens]
- **User Sees:** [What's displayed]
- **Next:** [Where they go next]
2. **[Stage 2 Name]** - [Page/Screen Name]
- **User Action:** [What user does]
- **System Response:** [What happens]
- **User Sees:** [What's displayed]
- **Next:** [Where they go next]
[Continue for all stages...]
### Journey Diagram
\`\`\`mermaid
graph TD
A[Entry Point] --> B[Stage 1]
B --> C[Stage 2]
C --> D[Stage 3]
D --> E[Success!]
\`\`\`
Add Touchpoints
For each stage, document:
- UI Elements: Buttons, forms, links
- Data Displayed: What information user sees
- User Emotions: Confident, confused, frustrated, delighted
- Time Spent: Typical duration at each stage (if known)
Phase 3: Map Alternative Paths
Document Alternate Journeys
Map common variations:
- New user vs returning user
- Mobile vs desktop
- Different user permissions/roles
- Feature variations (A/B tests)
## Alternate Journey: [Variation Name]
**Difference from Primary:** [How it differs]
**When This Occurs:** [Conditions]
### Journey Diagram
\`\`\`mermaid
graph TD
A[Entry] --> B{User Type?}
B -->|New| C[Onboarding]
B -->|Returning| D[Skip to Main]
C --> E[Success]
D --> E
\`\`\`
Phase 4: Map Error & Edge Cases
Document Error Paths
Map what happens when things go wrong:
## Error Journeys
### 1. [Error Scenario Name]
**Trigger:** [What causes this error]
**User Impact:** [How user is affected]
**Recovery Path:**
1. User sees error message: "[Message text]"
2. User can: [Action options]
3. System: [What happens]
4. Result: [Back to happy path or exit]
\`\`\`mermaid
graph TD
A[Action] -->|Error| B[Error Message]
B --> C{User Choice}
C -->|Retry| A
C -->|Cancel| D[Exit]
\`\`\`
Map Abandonment Points
Identify where users typically exit:
- High friction points (complex forms, slow loading)
- Confusion points (unclear next step)
- Blockers (missing info, errors)
## Abandonment Analysis
### Common Exit Points
1. **[Stage Name]** - [Location]
- **Why:** [Reason users abandon]
- **Frequency:** High | Medium | Low
- **Prevention:** [How to reduce abandonment]
Phase 5: Add UX Insights
Document User Experience
For each journey stage, add:
## UX Insights
### [Stage Name]
**User Emotion:** 😊 Delighted | 😐 Neutral | 😟 Frustrated
**Complexity:** Simple | Moderate | Complex
**Common Questions:** [What users wonder at this stage]
**Pain Points:** [What causes friction]
**Opportunities:** [How to improve]
Add Metrics (if available)
Include analytics data if known:
- Conversion rate: % who complete journey
- Drop-off rate: % who abandon at each stage
- Time spent: Average duration per stage
- Success rate: % who achieve goal
Phase 6: Review & Save
Present Draft to User
I've mapped the user journey for [feature name]:
- Primary journey ([N] stages)
- [N] alternate paths
- [N] error scenarios
- UX insights for each stage
Review before I save.
Save Journey Map
Save to docs/journeys/[feature-name]-journey.md
Summarize Next Steps
User journey map created at: docs/journeys/[feature-name]-journey.md
Next steps:
1. Review with UX designer and product owner
2. Identify opportunities for improvement
3. Use as input for wireframes/mockups
4. Reference when creating test plans
5. Update as feature evolves
Output Format Template
# User Journey: [Feature Name]
**Generated:** YYYY-MM-DD
**Feature:** [Brief description]
**Primary User:** [User type]
---
## Overview
**User Goal:** [What user wants to accomplish]
**Entry Points:** [How users discover/start]
**Success Outcome:** [What success looks like]
**Typical Duration:** [If known, how long journey takes]
---
## Primary Journey: [Goal Name]
### Journey Steps
#### 1. [Stage Name] - [Page/Screen]
**User Action:** [What they do]
**System Response:** [What happens]
**User Sees:** [What's displayed]
**User Emotion:** 😊 | 😐 | 😟
**Next Step:** [Where they go]
**UI Elements:**
- [Button/link name]
- [Form fields]
- [Navigation]
**Pain Points:**
- [Any friction or confusion]
**Opportunities:**
- [Ways to improve this stage]
---
[Repeat for each stage]
---
### Journey Diagram
\`\`\`mermaid
graph TD
A[Entry Point] --> B[Stage 1: Discover]
B --> C[Stage 2: Engage]
C --> D[Stage 3: Act]
D --> E[Stage 4: Confirm]
E --> F[Success!]
C -.->|Error| G[Error Handler]
G --> C
style F fill:#90EE90
style G fill:#FFB6C1
\`\`\`
---
## Alternate Journeys
### Returning User Path
**Difference:** Skips onboarding, has saved preferences
**When:** User has account and is logged in
\`\`\`mermaid
graph TD
A{User Type?} -->|New| B[Full Onboarding]
A -->|Returning| C[Skip to Main]
B --> D[Main Flow]
C --> D
\`\`\`
---
## Error Journeys
### 1. [Error Scenario]
**Trigger:** [What causes error]
**User Impact:** [How user affected]
**Recovery:**
1. Error message shown
2. User can [action]
3. System [response]
---
## Abandonment Analysis
### Common Exit Points
| Stage | Exit Rate | Reason | Prevention |
|-------|-----------|--------|------------|
| [Stage] | High/Med/Low | [Why] | [How to reduce] |
---
## UX Insights
### Overall Journey
**Strengths:**
- [What works well]
**Pain Points:**
- [What causes friction]
**Opportunities:**
- [How to improve]
### Metrics (if available)
- **Completion Rate:** X%
- **Average Duration:** X minutes
- **Drop-off Points:** [List stages]
---
## Next Steps
- [ ] Review with UX team
- [ ] Create wireframes for key stages
- [ ] Identify quick wins for UX improvements
- [ ] Set up analytics tracking for journey stages
- [ ] Plan A/B tests for optimization
---
*User journey map generated by agentbootup user-journey-mapper skill*
Key Principles
- User-Centric: Focus on user actions and emotions, not system internals
- Visual: Use Mermaid diagrams to show flow clearly
- Complete: Include happy path, alternatives, and errors
- Actionable: Identify pain points and opportunities
- Honest: Document real user experience, not ideal scenario
- No Arbitrary Timeframes: Show sequence and dependencies, not schedules
When to Use
Use user-journey-mapper when:
- ✅ Designing new feature UX
- ✅ Understanding existing user flows
- ✅ Identifying UX pain points
- ✅ Planning UX improvements
- ✅ Documenting workflows for stakeholders
Use test-plan-generator instead when:
- ❌ Need E2E test cases with steps
- ❌ Validating feature functionality
- ❌ Creating QA test documentation
- ❌ Tracking bugs and issues
Integration with Other Skills
- Before prd-writer: Map journey first, then write requirements
- Before test-plan-generator: Journey informs test scenarios
- After user-story-generator: Visualize how stories connect in user flow
- With UX design: Use as input for wireframes and prototypes
Differences from Test Plan Generator
| Aspect |
user-journey-mapper |
test-plan-generator |
| Purpose |
UX design and workflow documentation |
Feature E2E testing |
| Focus |
User experience and flow |
Functionality and validation |
| Output |
Journey maps with diagrams |
Test cases with steps |
| Audience |
UX designers, product owners |
QA engineers, developers |
| When |
Before/during design |
After implementation |
| Includes |
Emotions, pain points, opportunities |
Prerequisites, smoke tests, issue tracking |
Target Audience
- UX designers planning user experience
- Product owners understanding user needs
- Developers implementing user flows
- Stakeholders visualizing how feature works
- Marketing understanding customer journey
1---2name: user-journey-mapper3description: Map user flows and journeys through your application for UX design and workflow visualization, independent of testing.4category: documentation5metadata:6 source: https://skillmd.com/skills/dundas/user-journey-mapper7---89# User Journey Mapper1011## Goal12Create visual user journey maps that document how users flow through your application to accomplish their goals. Ideal for UX design, workflow documentation, and understanding user experience before or after implementation.1314## Input15- **Feature description** - What the feature does16- **User goal** - What users want to accomplish17- **Entry point** - Where users start (homepage, email link, etc.)1819## Output20- **Format:** Markdown (`.md`) with Mermaid diagrams21- **Location:** `docs/journeys/`22- **Filename:** `[feature-name]-journey.md`2324---2526## Process2728### Phase 1: Context Gathering29301. **Ask Journey Questions**3132 ```33 I'll help map the user journey for [feature name].3435 Questions:36 1. Where does the user start? (homepage, email, notification, etc.)37 2. What is their end goal? (complete purchase, send message, etc.)38 3. Are there different paths to the same goal?39 4. What are common distractions or exit points?40 5. Any existing user flow diagrams or wireframes?41 ```42432. **Identify Journey Stages**4445 Map the typical journey stages:46 - **Awareness:** How do users discover this feature?47 - **Entry:** Where do they enter the flow?48 - **Engagement:** What actions do they take?49 - **Conversion:** What's the success action?50 - **Exit:** How do they leave (success, abandon, error)?5152### Phase 2: Map Primary Journey53543. **Document Happy Path**5556 Map the ideal, successful user journey:5758 ```markdown59 ## Primary Journey: [Goal Name]6061 **User Goal:** [What user wants to accomplish]62 **Entry Point:** [Where they start]63 **Success Outcome:** [What success looks like]6465 ### Journey Steps6667 1. **[Stage 1 Name]** - [Page/Screen Name]68 - **User Action:** [What user does]69 - **System Response:** [What happens]70 - **User Sees:** [What's displayed]71 - **Next:** [Where they go next]7273 2. **[Stage 2 Name]** - [Page/Screen Name]74 - **User Action:** [What user does]75 - **System Response:** [What happens]76 - **User Sees:** [What's displayed]77 - **Next:** [Where they go next]7879 [Continue for all stages...]8081 ### Journey Diagram8283 \`\`\`mermaid84 graph TD85 A[Entry Point] --> B[Stage 1]86 B --> C[Stage 2]87 C --> D[Stage 3]88 D --> E[Success!]89 \`\`\`90 ```91924. **Add Touchpoints**9394 For each stage, document:95 - **UI Elements:** Buttons, forms, links96 - **Data Displayed:** What information user sees97 - **User Emotions:** Confident, confused, frustrated, delighted98 - **Time Spent:** Typical duration at each stage (if known)99100### Phase 3: Map Alternative Paths1011025. **Document Alternate Journeys**103104 Map common variations:105 - **New user vs returning user**106 - **Mobile vs desktop**107 - **Different user permissions/roles**108 - **Feature variations (A/B tests)**109110 ```markdown111 ## Alternate Journey: [Variation Name]112113 **Difference from Primary:** [How it differs]114 **When This Occurs:** [Conditions]115116 ### Journey Diagram117118 \`\`\`mermaid119 graph TD120 A[Entry] --> B{User Type?}121 B -->|New| C[Onboarding]122 B -->|Returning| D[Skip to Main]123 C --> E[Success]124 D --> E125 \`\`\`126 ```127128### Phase 4: Map Error & Edge Cases1291306. **Document Error Paths**131132 Map what happens when things go wrong:133134 ```markdown135 ## Error Journeys136137 ### 1. [Error Scenario Name]138139 **Trigger:** [What causes this error]140 **User Impact:** [How user is affected]141142 **Recovery Path:**143 1. User sees error message: "[Message text]"144 2. User can: [Action options]145 3. System: [What happens]146 4. Result: [Back to happy path or exit]147148 \`\`\`mermaid149 graph TD150 A[Action] -->|Error| B[Error Message]151 B --> C{User Choice}152 C -->|Retry| A153 C -->|Cancel| D[Exit]154 \`\`\`155 ```1561577. **Map Abandonment Points**158159 Identify where users typically exit:160 - **High friction points** (complex forms, slow loading)161 - **Confusion points** (unclear next step)162 - **Blockers** (missing info, errors)163164 ```markdown165 ## Abandonment Analysis166167 ### Common Exit Points168169 1. **[Stage Name]** - [Location]170 - **Why:** [Reason users abandon]171 - **Frequency:** High | Medium | Low172 - **Prevention:** [How to reduce abandonment]173 ```174175### Phase 5: Add UX Insights1761778. **Document User Experience**178179 For each journey stage, add:180181 ```markdown182 ## UX Insights183184 ### [Stage Name]185186 **User Emotion:** 😊 Delighted | 😐 Neutral | 😟 Frustrated187 **Complexity:** Simple | Moderate | Complex188 **Common Questions:** [What users wonder at this stage]189 **Pain Points:** [What causes friction]190 **Opportunities:** [How to improve]191 ```1921939. **Add Metrics (if available)**194195 Include analytics data if known:196 - **Conversion rate:** % who complete journey197 - **Drop-off rate:** % who abandon at each stage198 - **Time spent:** Average duration per stage199 - **Success rate:** % who achieve goal200201### Phase 6: Review & Save20220310. **Present Draft to User**204 ```205 I've mapped the user journey for [feature name]:206 - Primary journey ([N] stages)207 - [N] alternate paths208 - [N] error scenarios209 - UX insights for each stage210211 Review before I save.212 ```21321411. **Save Journey Map**215 Save to `docs/journeys/[feature-name]-journey.md`21621712. **Summarize Next Steps**218 ```219 User journey map created at: docs/journeys/[feature-name]-journey.md220221 Next steps:222 1. Review with UX designer and product owner223 2. Identify opportunities for improvement224 3. Use as input for wireframes/mockups225 4. Reference when creating test plans226 5. Update as feature evolves227 ```228229---230231## Output Format Template232233```markdown234# User Journey: [Feature Name]235236**Generated:** YYYY-MM-DD237**Feature:** [Brief description]238**Primary User:** [User type]239240---241242## Overview243244**User Goal:** [What user wants to accomplish]245**Entry Points:** [How users discover/start]246**Success Outcome:** [What success looks like]247**Typical Duration:** [If known, how long journey takes]248249---250251## Primary Journey: [Goal Name]252253### Journey Steps254255#### 1. [Stage Name] - [Page/Screen]256257**User Action:** [What they do]258**System Response:** [What happens]259**User Sees:** [What's displayed]260**User Emotion:** 😊 | 😐 | 😟261**Next Step:** [Where they go]262263**UI Elements:**264- [Button/link name]265- [Form fields]266- [Navigation]267268**Pain Points:**269- [Any friction or confusion]270271**Opportunities:**272- [Ways to improve this stage]273274---275276[Repeat for each stage]277278---279280### Journey Diagram281282\`\`\`mermaid283graph TD284 A[Entry Point] --> B[Stage 1: Discover]285 B --> C[Stage 2: Engage]286 C --> D[Stage 3: Act]287 D --> E[Stage 4: Confirm]288 E --> F[Success!]289290 C -.->|Error| G[Error Handler]291 G --> C292293 style F fill:#90EE90294 style G fill:#FFB6C1295\`\`\`296297---298299## Alternate Journeys300301### Returning User Path302303**Difference:** Skips onboarding, has saved preferences304**When:** User has account and is logged in305306\`\`\`mermaid307graph TD308 A{User Type?} -->|New| B[Full Onboarding]309 A -->|Returning| C[Skip to Main]310 B --> D[Main Flow]311 C --> D312\`\`\`313314---315316## Error Journeys317318### 1. [Error Scenario]319320**Trigger:** [What causes error]321**User Impact:** [How user affected]322323**Recovery:**3241. Error message shown3252. User can [action]3263. System [response]327328---329330## Abandonment Analysis331332### Common Exit Points333334| Stage | Exit Rate | Reason | Prevention |335|-------|-----------|--------|------------|336| [Stage] | High/Med/Low | [Why] | [How to reduce] |337338---339340## UX Insights341342### Overall Journey343344**Strengths:**345- [What works well]346347**Pain Points:**348- [What causes friction]349350**Opportunities:**351- [How to improve]352353### Metrics (if available)354355- **Completion Rate:** X%356- **Average Duration:** X minutes357- **Drop-off Points:** [List stages]358359---360361## Next Steps362363- [ ] Review with UX team364- [ ] Create wireframes for key stages365- [ ] Identify quick wins for UX improvements366- [ ] Set up analytics tracking for journey stages367- [ ] Plan A/B tests for optimization368369---370371*User journey map generated by agentbootup user-journey-mapper skill*372```373374---375376## Key Principles377378- **User-Centric:** Focus on user actions and emotions, not system internals379- **Visual:** Use Mermaid diagrams to show flow clearly380- **Complete:** Include happy path, alternatives, and errors381- **Actionable:** Identify pain points and opportunities382- **Honest:** Document real user experience, not ideal scenario383- **No Arbitrary Timeframes:** Show sequence and dependencies, not schedules384385---386387## When to Use388389Use **user-journey-mapper** when:390- ✅ Designing new feature UX391- ✅ Understanding existing user flows392- ✅ Identifying UX pain points393- ✅ Planning UX improvements394- ✅ Documenting workflows for stakeholders395396Use **test-plan-generator** instead when:397- ❌ Need E2E test cases with steps398- ❌ Validating feature functionality399- ❌ Creating QA test documentation400- ❌ Tracking bugs and issues401402---403404## Integration with Other Skills405406- **Before prd-writer:** Map journey first, then write requirements407- **Before test-plan-generator:** Journey informs test scenarios408- **After user-story-generator:** Visualize how stories connect in user flow409- **With UX design:** Use as input for wireframes and prototypes410411---412413## Differences from Test Plan Generator414415| Aspect | user-journey-mapper | test-plan-generator |416|--------|---------------------|---------------------|417| **Purpose** | UX design and workflow documentation | Feature E2E testing |418| **Focus** | User experience and flow | Functionality and validation |419| **Output** | Journey maps with diagrams | Test cases with steps |420| **Audience** | UX designers, product owners | QA engineers, developers |421| **When** | Before/during design | After implementation |422| **Includes** | Emotions, pain points, opportunities | Prerequisites, smoke tests, issue tracking |423424---425426## Target Audience427428- UX designers planning user experience429- Product owners understanding user needs430- Developers implementing user flows431- Stakeholders visualizing how feature works432- Marketing understanding customer journey