journey-map
Create a customer journey map from elicited requirements. Visualizes end-to-end user experience with stages, touchpoints, emotions, and pain points. Outputs Mermaid diagrams.
What this skill does
# Journey Map Command
Create customer journey maps from elicited requirements, visualizing the complete user experience.
## Usage
```bash
/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:
```yaml
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:
```yaml
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:
```yaml
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:
```yaml
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)
```mermaid
%%{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
```mermaid
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
```yaml
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
```markdown
# 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
1. **Onboarding Complexity** (Score: 2)
- Stage: Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work โ this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.