customer-journey-map

Engineering Community

Repo stars 11,899
Author repo pm-skills

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping t…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Customer Journey Map”, “Context”, “Instructions”, “Further Reading”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name customer-journey-map directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Customer Journey Map / Context / Instructions” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

Context

You are creating a customer journey map for $ARGUMENTS.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

Instructions

Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

Map the journey stages (adapt to the product):

Stage	Description
Awareness	How do they first learn about the product?
Consideration	What do they evaluate? What alternatives do they compare?
Acquisition	How do they sign up or purchase?
Onboarding	First experience with the product — time to value
Engagement	Regular usage — building habits
Retention	What keeps them coming back? What might cause churn?
Advocacy	When and why do they recommend the product to others?

For each stage, document:
- Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
- User actions: What they do at this stage
- Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
- Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
- Pain points: Friction, confusion, drop-off risks
- Opportunities: How to improve the experience at this point
Identify critical moments:
- Aha moment: When the user first experiences core value
- Moments of truth: Decision points where they commit or abandon
- Churn triggers: Where users most commonly drop off
Create the journey map table:

Stage Touchpoint User Action Emotion Pain Point Opportunity
Recommend prioritized improvements:
- Which pain points have the highest impact on conversion or retention?
- What quick wins can improve the experience immediately?
- What requires deeper investment but has the biggest payoff?

Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @phuryn · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview customer-journey-map.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

## Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

### Context

You are creating a customer journey map for **$ARGUMENTS**.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

### Instructions

1. **Define the persona**: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

2. **Map the journey stages** (adapt to the product):

   | Stage | Description |
   |---|---|
   | **Awareness** | How do they first learn about the product? |
   | **Consideration** | What do they evaluate? What alternatives do they compare? |
   | **Acquisition** | How do they sign up or purchase? |
   | **Onboarding** | First experience with the product — time to value |
   | **Engagement** | Regular usage — building habits |
   | **Retention** | What keeps them coming back? What might cause churn? |
   | **Advocacy** | When and why do they recommend the product to others? |

3. **For each stage, document**:

   - **Touchpoints**: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
   - **User actions**: What they do at this stage
   - **Thoughts & questions**: What's on their mind ("Is this worth my time?" "How do I...?")
   - **Emotions**: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
   - **Pain points**: Friction, confusion, drop-off risks
   - **Opportunities**: How to improve the experience at this point

4. **Identify critical moments**:

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Customer Journey Map → Context → Instructions → Further Reading
terms    -> $ARGUMENTS · Define the persona · Map the journey stages · Awareness · Consideration · Acquisition · Onboarding · Engagement
files/cmd -> www.productcompass.pm/p/user-journey-mapping-101 · www.productcompass.pm/p/funnel-analysis · www.productcompass.pm/p/market-research-advanced-techniques · www.productcompass.pm/p/interviewing-customers-the-ultimate
body sha256 -> 3417e7d19081