journey-map
SKILL.md
Journey Map Command
Create customer journey maps from elicited requirements, visualizing the complete user experience.
Usage
/requirements-elicitation:journey-map
/requirements-elicitation:journey-map --domain "onboarding"
/requirements-elicitation:journey-map --domain "checkout" --persona "first-time-buyer"
/requirements-elicitation:journey-map --domain "support" --format mermaid
Arguments
| Argument | Required | Description |
|---|---|---|
| --domain | No | Domain to map (default: current/most recent) |
| --persona | No | Specific persona to map (default: primary user) |
| --format | No | Output format: mermaid, yaml, markdown (default: mermaid) |
Workflow
Step 1: Load Synthesized Requirements
Read from .requirements/{domain}/synthesis/ and .requirements/{domain}/interview/ folders.
Step 2: Identify Journey Stages
Map the end-to-end experience from first awareness to post-completion:
journey_stages:
awareness:
description: "User becomes aware of need/problem"
questions:
- "What triggers the user to start?"
- "How do they discover the solution?"
consideration:
description: "User evaluates options"
questions:
- "What alternatives do they consider?"
- "What information do they need?"
acquisition:
description: "User obtains the solution"
questions:
- "How do they sign up/purchase?"
- "What's the onboarding experience?"
service:
description: "User uses the solution"
questions:
- "What's the day-to-day experience?"
- "What tasks do they perform?"
loyalty:
description: "User becomes repeat customer"
questions:
- "What brings them back?"
- "Would they recommend to others?"
Step 3: Map Touchpoints
Identify all interaction points in each stage:
touchpoint_types:
digital:
- Website
- Mobile app
- Email
- SMS
human:
- Customer service
- Sales
- Support chat
physical:
- Store
- Package
- Documentation
Step 4: Capture Emotional Journey
Document user emotions at each stage:
emotional_journey:
positive:
- Excited
- Confident
- Satisfied
- Delighted
neutral:
- Curious
- Focused
- Waiting
negative:
- Frustrated
- Confused
- Anxious
- Disappointed
Step 5: Identify Pain Points and Opportunities
Extract from requirements and interviews:
analysis:
pain_points:
- Source: Interview transcript, stakeholder complaint
- Location: Which stage/touchpoint
- Severity: Critical, Major, Minor
opportunities:
- Gap in current experience
- Unmet need from requirements
- Potential delight moment
Step 6: Generate Output
Create the journey map in the requested format.
Output Formats
Mermaid Diagram (Default)
%%{init: {'theme': 'base'}}%%
journey
title Customer Onboarding Journey
section Awareness
Discover product online: 5: Customer
Read reviews: 4: Customer
Visit website: 4: Customer
section Consideration
Compare features: 3: Customer
Request demo: 4: Customer, Sales
Evaluate pricing: 3: Customer
section Acquisition
Sign up for trial: 4: Customer
Complete onboarding: 3: Customer, Support
Make first purchase: 5: Customer
section Service
Use product daily: 4: Customer
Contact support: 2: Customer, Support
Discover new features: 5: Customer
section Loyalty
Renew subscription: 5: Customer
Refer friends: 5: Customer
Alternative: Flowchart Style
flowchart LR
subgraph Awareness["π Awareness"]
A1["Discover<br/>π Curious"]
A2["Research<br/>π€ Evaluating"]
end
subgraph Consideration["βοΈ Consideration"]
C1["Compare<br/>π Uncertain"]
C2["Demo<br/>π Interested"]
end
subgraph Acquisition["π Acquisition"]
Q1["Sign Up<br/>π Excited"]
Q2["Onboard<br/>π€ Frustrated"]
Q3["First Use<br/>π Satisfied"]
end
subgraph Service["βοΈ Service"]
S1["Daily Use<br/>π Confident"]
S2["Support<br/>π€ Frustrated"]
end
subgraph Loyalty["β€οΈ Loyalty"]
L1["Renew<br/>π Loyal"]
L2["Refer<br/>π Advocate"]
end
A1 --> A2 --> C1 --> C2 --> Q1 --> Q2 --> Q3 --> S1 --> S2 --> L1 --> L2
style Q2 fill:#ffcdd2
style S2 fill:#ffcdd2
YAML Export
journey_map:
title: "Customer Onboarding Journey"
domain: "onboarding"
persona: "first-time-user"
created: "2025-12-26"
stages:
- name: "Awareness"
emoji: "π"
touchpoints:
- name: "Discover product online"
channel: "Search / Social"
emotion: "curious"
score: 5
- name: "Read reviews"
channel: "Review sites"
emotion: "evaluating"
score: 4
- name: "Consideration"
emoji: "βοΈ"
touchpoints:
- name: "Compare features"
channel: "Website"
emotion: "uncertain"
score: 3
pain_point: "Hard to find comparison information"
- name: "Request demo"
channel: "Sales call"
emotion: "interested"
score: 4
- name: "Acquisition"
emoji: "π"
touchpoints:
- name: "Sign up for trial"
channel: "Website"
emotion: "excited"
score: 4
- name: "Complete onboarding"
channel: "App"
emotion: "frustrated"
score: 2
pain_point: "Onboarding too complex, too many steps"
opportunity: "Simplify to 3-step wizard"
- name: "Service"
emoji: "βοΈ"
touchpoints:
- name: "Daily use"
channel: "App"
emotion: "confident"
score: 4
- name: "Contact support"
channel: "Chat / Email"
emotion: "frustrated"
score: 2
pain_point: "Long wait times, repeated explanations"
- name: "Loyalty"
emoji: "β€οΈ"
touchpoints:
- name: "Renew subscription"
channel: "Email / App"
emotion: "loyal"
score: 5
- name: "Refer friends"
channel: "Word of mouth"
emotion: "advocate"
score: 5
opportunity: "Add referral rewards program"
summary:
overall_score: 3.8
critical_pain_points:
- "Onboarding complexity"
- "Support wait times"
key_opportunities:
- "Simplify onboarding wizard"
- "Add self-service support"
- "Implement referral program"
Markdown Export
# Customer Journey Map: Onboarding
**Persona:** First-Time User
**Domain:** Onboarding
**Created:** 2025-12-26
## Journey Overview
| Stage | Touchpoint | Channel | Emotion | Score |
|-------|------------|---------|---------|-------|
| π Awareness | Discover online | Search | π Curious | 5 |
| π Awareness | Read reviews | Review sites | π€ Evaluating | 4 |
| βοΈ Consideration | Compare features | Website | π Uncertain | 3 |
| βοΈ Consideration | Request demo | Sales | π Interested | 4 |
| π Acquisition | Sign up | Website | π Excited | 4 |
| π Acquisition | Onboarding | App | π€ **Frustrated** | 2 |
| βοΈ Service | Daily use | App | π Confident | 4 |
| βοΈ Service | Contact support | Chat | π€ **Frustrated** | 2 |
| β€οΈ Loyalty | Renew | App | π Loyal | 5 |
| β€οΈ Loyalty | Refer friends | Word of mouth | π Advocate | 5 |
## Emotional Journey Curve
```text
π | *
π | * * * * *
π | *
π€ | * *
+-------------------------------------------------->
Aware Research Compare Demo Sign Onboard Use Support Renew Refer
Pain Points
Critical
-
Onboarding Complexity (Score: 2)
- Stage: Acquisition
- Issue: Too many steps, confusing flow
- Recommendation: Simplify to 3-step wizard
-
Support Wait Times (Score: 2)
- Stage: Service
- Issue: Long waits, repeated explanations
- Recommendation: Add self-service options
Opportunities
- Simplify Onboarding - High impact, addresses critical pain point
- Self-Service Support - Reduce frustration, lower costs
- Referral Program - Capitalize on advocate stage
Example Session
/requirements-elicitation:journey-map --domain "e-commerce" --persona "mobile-shopper"
Loading synthesis: .requirements/e-commerce/synthesis/SYN-20251226-150000.yaml
Loading interviews: .requirements/e-commerce/interview/*.yaml
Persona: Mobile Shopper
- Primary device: Smartphone
- Shopping frequency: Weekly
- Key motivations: Convenience, quick checkout
Identifying journey stages...
β Awareness (3 touchpoints)
β Consideration (4 touchpoints)
β Acquisition (5 touchpoints)
β Service (3 touchpoints)
β Loyalty (2 touchpoints)
Mapping emotional journey...
Critical pain points identified: 2
- Mobile checkout flow (Score: 2)
- Product search on small screen (Score: 3)
Delight moments identified: 3
- Quick reorder feature (Score: 5)
- Order tracking notifications (Score: 5)
- One-tap checkout (Score: 5)
Generating Mermaid diagram...
[Mermaid diagram output]
Saved to: .requirements/e-commerce/journey-map/
- journey-map-mobile-shopper.mmd
- journey-map-mobile-shopper.yaml
Output Locations
output_locations:
mermaid: ".requirements/{domain}/journey-map/journey-map[-{persona}].mmd"
yaml: ".requirements/{domain}/journey-map/journey-map[-{persona}].yaml"
markdown: ".requirements/{domain}/journey-map/journey-map[-{persona}].md"
Integration with Other Commands
After Simulation
# Simulate stakeholder perspectives
/requirements-elicitation:simulate --domain "onboarding" --personas end-user
# Create journey map from simulation insights
/requirements-elicitation:journey-map --domain "onboarding"
Combined with Story Mapping
# Create both views for comprehensive understanding
/requirements-elicitation:journey-map --domain "checkout"
/requirements-elicitation:story-map --domain "checkout"
# Journey map = emotional experience view
# Story map = delivery/release planning view
Delegation
This command delegates to the journey-mapper agent for complex journey analysis and visualization generation.
Error Handling
error_handling:
no_synthesis:
message: "No synthesized requirements found for domain"
action: "Run /discover first to elicit requirements"
no_persona_data:
message: "No persona information available"
action: "Proceed with generic 'user' persona or run /simulate first"
insufficient_touchpoints:
message: "Too few touchpoints for meaningful journey map"
action: "Add more requirements or interview data"
Weekly Installs
1
Repository
melodic-softwarβ¦-pluginsGitHub Stars
38
First Seen
11 days ago
Security Audits
Installed on
amp1
cline1
augment1
opencode1
cursor1
kimi-cli1