Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

journey-mapping旅程地图

Agent Skill

journey-mapping 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

541

周安装

23

GitHub Stars

61

下载量

190
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:journey-mapping(旅程地图)
来源仓库:https://github.com/melodic-software/claude-code-plugins
仓库路径:skills/journey-mapping
安装命令:
npx skills add https://github.com/melodic-software/claude-code-plugins --skill journey-mapping
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill journey-mapping

简介

用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装并使用。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • journey-mapping 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Journey Mapping

Create user and customer journey maps to understand experiences, identify pain points, and discover improvement opportunities. A human-centered complement to process-focused value stream mapping.

What is a Journey Map?

A journey map visualizes a user's experience over time as they accomplish a goal. Unlike process maps (which show what happens), journey maps show how it feels from the user's perspective.

ElementDefinitionPurpose
PersonaWho is taking the journeyFocus on specific user type
PhasesMajor stages of the journeyOrganize the experience
TouchpointsInteractions with your systemIdentify contact points
ActionsWhat the user doesUnderstand behavior
ThoughtsWhat the user thinksUnderstand mindset
EmotionsHow the user feelsIdentify emotional peaks/valleys
Pain PointsFriction and frustrationsTarget improvements
OpportunitiesWays to improvePrioritize enhancements

Journey Types

TypeScopeWhen to Use
Current StateHow things are todayIdentify problems
Future StateDesired experienceDesign solutions
Day-in-the-LifeFull day across contextsUnderstand broader context
Service BlueprintJourney + backstage operationsDesign service delivery

Workflow

Phase 1: Preparation

Step 1: Define the Journey Scope

## Journey Definition

**Journey Name:** New Customer Onboarding
**Persona:** Sarah - First-time SaaS Buyer
**Goal:** Successfully adopt the product and get first value
**Trigger:** Signs up for trial
**End State:** Completes first project successfully
**Time Frame:** First 30 days

Step 2: Select or Create Persona

## Persona: Sarah - First-time SaaS Buyer

**Demographics:**
- Age: 32
- Role: Marketing Manager
- Company: Mid-size B2B
- Tech Savviness: Moderate

**Goals:**
- Streamline team workflows
- Prove ROI to leadership
- Look good to her team

**Frustrations:**
- Limited time to learn new tools
- Past bad experiences with complex software
- Pressure to show quick results

**Quote:** "I need something that works out of the box."

Phase 2: Map the Journey

Step 1: Identify Phases

Typical journey phases:

DomainCommon Phases
PurchaseAwareness → Consideration → Decision → Purchase
OnboardingSign-up → Setup → First Use → Habit Formation
SupportIssue → Search → Contact → Resolution → Follow-up
RenewalReview → Evaluate → Negotiate → Renew/Churn

Step 2: Map Touchpoints and Actions

For each phase:

## Phase: Setup

### Touchpoints
- Welcome email
- Product UI (setup wizard)
- Help documentation
- Onboarding video

### Actions
1. Opens welcome email
2. Clicks "Get Started"
3. Enters company info
4. Invites team members
5. Configures first workspace

Step 3: Capture Thoughts and Emotions

## Phase: Setup - Experience

| Step | Thought | Emotion | Intensity |
|------|---------|---------|-----------|
| Opens email | "Let's see if this is worth it" | Curious, skeptical | Neutral |
| Clicks Get Started | "Okay, here we go" | Hopeful | Slightly positive |
| Company info form | "Why so many fields?" | Frustrated | Negative |
| Invites team | "Easy enough" | Relieved | Positive |
| First workspace | "This is actually nice!" | Pleased | Very positive |

Step 4: Identify Pain Points

## Pain Points - Setup Phase

| Pain Point | Severity | Evidence | Root Cause |
|------------|----------|----------|------------|
| Too many required fields | High | Drop-off data, complaints | Legacy form design |
| Unclear field labels | Medium | Support tickets | Jargon-heavy copy |
| No save-and-continue | High | Abandoned setups | Technical limitation |
| Team invite confusion | Medium | Support volume | Poor UX |

Step 5: Identify Opportunities

## Opportunities - Setup Phase

| Opportunity | Impact | Effort | Priority |
|-------------|--------|--------|----------|
| Progressive disclosure (fewer upfront fields) | High | Low | 1 |
| Save progress functionality | High | Medium | 2 |
| Contextual help tooltips | Medium | Low | 3 |
| Interactive setup tutorial | Medium | High | 4 |

Phase 3: Visualize the Journey

Standard Journey Map Format

PHASE:      | Awareness    | Sign-up      | Setup        | First Use    | Habit
------------|--------------|--------------|--------------|--------------|--------
TOUCHPOINTS | Ads, blog    | Landing page | Email, UI    | Product      | Product
            |              | pricing page | docs         |              | email
------------|--------------|--------------|--------------|--------------|--------
ACTIONS     | Researches   | Compares     | Creates      | Explores     | Daily
            | solutions    | plans        | account      | features     | usage
------------|--------------|--------------|--------------|--------------|--------
THOUGHTS    | "Is there    | "Which plan  | "This is     | "How do I    | "This
            | a better     | is right?"   | taking       | do X?"       | saves
            | way?"        |              | too long"    |              | time"
------------|--------------|--------------|--------------|--------------|--------
EMOTIONS    |     😐       |      🤔      |      😣      |      😕      |     😊
            |  Neutral     |   Uncertain  |  Frustrated  |   Confused   |  Happy
------------|--------------|--------------|--------------|--------------|--------
PAIN POINTS | Too many     | Pricing      | Long form    | Feature      | None
            | options      | confusion    | No save      | discoverability
------------|--------------|--------------|--------------|--------------|--------
OPPORTUN-   | Clear        | Simpler      | Reduce       | Better       | Celebrate
ITIES       | comparisons  | pricing      | friction     | onboarding   | wins

Phase 4: Emotion Curve

Visualize emotional highs and lows:

EMOTION
  😊 +2  |                                              ___/
  😌 +1  |         ___/\                              /
  😐  0  |____/\__/      \            ___           /
  😕 -1  |                \          /   \__      _/
  😣 -2  |                 \________/          \_/

         |--Awareness--|--Sign-up--|--Setup--|--First Use--|--Habit--|
                                      ↑
                               Pain Point: Long form

Phase 5: Identify Moments of Truth

Moments of Truth are critical interactions that disproportionately impact the overall experience:

Moment TypeDefinitionExample
Zero Moment of Truth (ZMOT)Pre-purchase researchReading reviews
First Moment of Truth (FMOT)Initial encounterLanding page
Second Moment of Truth (SMOT)Using the productFirst workflow
Ultimate Moment of Truth (UMOT)Sharing experienceReferral/review
## Moments of Truth

| Moment | Phase | Current Experience | Desired Experience |
|--------|-------|-------------------|-------------------|
| FMOT | Landing | Overwhelming options | Clear value prop |
| SMOT | First Use | Confusion, need help | Guided success |
| UMOT | Habit | No celebration | Achievement sharing |

Output Formats

Narrative Summary

## Journey Map Summary

**Journey:** [Name]
**Persona:** [Name]
**Date:** [ISO date]
**Analyst:** journey-facilitator

### Journey Overview
[2-3 sentence summary of the end-to-end experience]

### Emotional Journey
- **Highest Point:** [Phase] - [Why]
- **Lowest Point:** [Phase] - [Why]
- **Overall Arc:** [Description]

### Critical Pain Points
1. **[Pain Point]** (Phase: [X]) - [Impact and evidence]
2. **[Pain Point]** (Phase: [X]) - [Impact and evidence]

### Top Opportunities
1. **[Opportunity]** - Impact: High, Effort: Low
2. **[Opportunity]** - Impact: High, Effort: Medium

### Moments of Truth
- **Make or Break Moment:** [Description]
- **Current State:** [Assessment]
- **Recommendation:** [Action]

Structured Data (YAML)

journey_map:
  name: "New Customer Onboarding"
  version: "1.0"
  date: "{ISO-8601-date}"
  analyst: "journey-facilitator"
  type: current_state

  persona:
    name: "Sarah"
    archetype: "First-time SaaS Buyer"
    goals:
      - "Get value quickly"
      - "Look good to leadership"
    frustrations:
      - "Limited time"
      - "Complex tools"

  journey:
    goal: "Successfully adopt and get first value"
    trigger: "Signs up for trial"
    end_state: "Completes first project"
    time_frame: "30 days"

  phases:
    - name: "Awareness"
      order: 1
      touchpoints:
        - channel: "Web"
          type: "Blog post"
        - channel: "Email"
          type: "Marketing email"
      actions:
        - "Researches solutions"
        - "Reads comparison articles"
      thoughts:
        - "Is there a better way?"
      emotions:
        overall: neutral
        intensity: 0
      pain_points: []
      opportunities:
        - name: "Clear comparison content"
          impact: medium
          effort: low

    - name: "Setup"
      order: 3
      touchpoints:
        - channel: "Email"
          type: "Welcome email"
        - channel: "Product"
          type: "Setup wizard"
      actions:
        - "Opens welcome email"
        - "Starts setup wizard"
        - "Enters company info"
      thoughts:
        - "This is taking too long"
        - "Why so many fields?"
      emotions:
        overall: frustrated
        intensity: -2
      pain_points:
        - description: "Long form with many required fields"
          severity: high
          evidence: "40% drop-off rate"
        - description: "No save-and-continue"
          severity: high
          evidence: "Support tickets"
      opportunities:
        - name: "Progressive disclosure"
          impact: high
          effort: low
        - name: "Save progress"
          impact: high
          effort: medium

  moments_of_truth:
    - type: "First Moment (FMOT)"
      phase: "Sign-up"
      current_state: "Overwhelming options"
      desired_state: "Clear value proposition"
      priority: high

    - type: "Second Moment (SMOT)"
      phase: "First Use"
      current_state: "Confusion, needs help"
      desired_state: "Guided success path"
      priority: high

  summary:
    emotion_arc: "Curious → Frustrated → Confused → Satisfied"
    highest_point:
      phase: "Habit"
      reason: "Realizes time savings"
    lowest_point:
      phase: "Setup"
      reason: "Long form, no progress saving"
    top_recommendation: "Reduce setup friction through progressive disclosure"

Mermaid Diagrams

Journey Flow:

journey
    title New Customer Onboarding Journey
    section Awareness
        Reads blog post: 5: Customer
        Watches demo video: 4: Customer
    section Sign-up
        Views pricing: 3: Customer
        Selects plan: 4: Customer
    section Setup
        Fills long form: 2: Customer
        Invites team: 4: Customer
    section First Use
        Explores features: 3: Customer
        Completes first task: 5: Customer
    section Habit
        Daily usage: 5: Customer

Emotion Curve (Mermaid XYChart):

xychart-beta
    title "Emotional Journey"
    x-axis ["Awareness", "Sign-up", "Setup", "First Use", "Habit"]
    y-axis "Emotion" -3 --> 3
    line [0, -1, -2, 1, 2]

Multi-Persona Workshop

For comprehensive journey analysis, run parallel persona agents:

Persona AgentPerspectiveFocus
first-time-user-personaNew to productOnboarding friction
power-user-personaExperiencedAdvanced needs
admin-personaManagementConfiguration, oversight
support-seeker-personaNeeds helpSupport experience

When to Use

ScenarioUse Journey Mapping?
UX redesignYes - understand current experience
Service designYes - design end-to-end experience
Customer complaintsYes - find pain points
Onboarding optimizationYes - improve adoption
Process improvementPartial - combine with VSM
Technical architectureNo - wrong level of abstraction

Integration

Upstream

  • stakeholder-analysis - Understand user stakeholders
  • process-modeling - Process context
  • Persona research - User research inputs

Downstream

  • Requirements - Experience requirements
  • UX design - Design improvements
  • value-stream-mapping - Operational improvements

Related Skills

  • value-stream-mapping - Process efficiency perspective
  • stakeholder-analysis - Stakeholder needs
  • capability-mapping - Capability touchpoints
  • root-cause-analysis - Investigate pain point causes
  • prioritization - Prioritize opportunities
  • decision-analysis - Evaluate improvement options

User-Facing Interface

When invoked directly by the user, this skill operates as follows.

Arguments

  • <journey-description>: Description of the journey to map (e.g., "customer purchasing a subscription")
  • --mode: Mapping mode (default: guided)

- full: Comprehensive journey with detailed touchpoint analysis (~10K tokens) - quick: Rapid journey mapping (~4K tokens) - guided: Interactive journey discovery (variable)

  • --persona: Optional persona name to use (creates new if not provided)
  • --dir: Output directory (default: docs/analysis/)

Execution Workflow

  1. Parse Arguments - Extract journey description, mode, and persona. If no description provided, ask the user who is taking the journey, what they are trying to accomplish, and where the journey starts and ends.
  2. Define or Select Persona - Use provided persona, create default from context (Quick/Full), or interactively define (Guided).
  3. Execute Based on Mode:

- Full: Spawn the journey-facilitator agent for thorough mapping with 4-6 phases, emotion curves, Moments of Truth (ZMOT/FMOT/SMOT/UMOT), and prioritized opportunities. - Quick: Rapid mapping with 4-5 phases, key touchpoints, obvious pain points, and top 3 opportunities. - Guided: Interactive discovery using AskUserQuestion for research approach and empathy depth, then walk through persona, scope, phases, phase deep-dives, moments of truth, and opportunities.

  1. Generate Output - Produce journey map markdown, Mermaid journey diagram, emotion curve (xychart-beta), pain point inventory, and opportunity backlog.
  2. Save Results - Save to docs/analysis/journey-map-[persona-name].md (or custom --dir).
  3. Suggest Follow-Ups - Recommend stakeholder-analysis for journey owners, value-stream-mapping for operations behind pain points, and capability-mapping for touchpoint-capability links.

Version History

  • v1.0.0 (2025-12-26): Initial release

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Antigravity

26.73%
按下载量换算51

Claude Code

22.47%
按下载量换算43

trae

16.8%
按下载量换算32

windsurf

12.98%
按下载量换算25

Codex

9.1%
按下载量换算17

Gemini CLI

3.44%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills