Map and analyze the customer journey across Awareness, Consideration, Decision, Usage, and Advocacy stages. Use this skill when the user needs to understand the customer experience end-to-end, identify drop-off points, optimize touchpoints, or improve conversion — even if they say 'where are we losing customers', 'what's our funnel look like', or 'map the user experience'.
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-customer-journey
Customer Journey Mapping visualizes the entire experience a customer has with a brand — from first awareness through post-purchase advocacy. It identifies touchpoints, emotions, pain points, and opportunities at each stage. The goal is to find and fix where customers get stuck, frustrated, or leave.
Trigger conditions:
When NOT to use:
IRON LAW: Map the Customer's Reality, Not Your Ideal
The journey map must reflect what customers ACTUALLY experience, not what
you designed or intended. If customers Google your brand and find negative
reviews (reality), don't map "customer visits our website" (ideal).
Base the map on data: analytics, customer interviews, support tickets,
heatmaps — not internal assumptions.
IRON LAW: Every Touchpoint Needs an Emotion
A journey map without emotions is a process diagram. At every touchpoint,
note the customer's emotional state: confident, confused, frustrated,
delighted. Emotions predict behavior better than process steps.
1. Awareness — Customer realizes they have a need or discovers your brand
2. Consideration — Customer evaluates options and compares alternatives
3. Decision — Customer chooses and purchases
4. Usage — Customer uses the product/service
5. Advocacy — Customer recommends (or warns against) the brand
Who is this journey for? Use the target segment from STP:
For each stage, list:
Find the 2-3 critical moments that disproportionately impact the overall experience:
Rank improvements by: Impact on customer satisfaction × Feasibility × Cost. Fix the highest-impact pain points first.
# Customer Journey Map: {Product/Service}
## Persona
- Name: {persona name}
- Profile: {segment description}
- Goal: {what they're trying to achieve}
## Journey Map
| Stage | Touchpoints | Actions | Emotion | Pain Points | Opportunities |
|-------|------------|---------|---------|-------------|---------------|
| Awareness | {list} | {what they do} | 😊/😐/😤 | {friction} | {improvement} |
| Consideration | ... | ... | ... | ... | ... |
| Decision | ... | ... | ... | ... | ... |
| Usage | ... | ... | ... | ... | ... |
| Advocacy | ... | ... | ... | ... | ... |
## Moments of Truth
1. **{moment}** — {why this is critical}
2. **{moment}** — {why this is critical}
## Priority Improvements
1. {Stage} → {specific improvement} — Impact: High, Effort: Low
2. ...
Scenario: Journey for a Taiwanese food delivery app (persona: 30-year-old office worker ordering lunch)
| Stage | Touchpoints | Emotion | Pain Point |
|-------|------------|---------|------------|
| Awareness | Colleague mentions app during lunch discussion | 😊 Curious | None — organic discovery |
| Consideration | Downloads app, browses restaurants, reads reviews | 😐 → 😤 | Too many choices, no "nearby + fast" filter |
| Decision | Selects restaurant, adds items, sees delivery fee + minimum order | 😤 | Delivery fee NT$60 feels expensive for a NT$120 lunch; minimum order forces buying more than needed |
| Usage | Waits for delivery, receives food, eats | 😊 → 😐 | Food arrives in 35 min (app said 25), packaging leaked |
| Advocacy | Doesn't refer friends | 😐 | No referral incentive; experience was "okay, not great" |
Moment of Truth: Decision stage — the delivery fee shock causes 40% cart abandonment (data-backed ✓).
What went wrong:
references/service-blueprint.mdCreate SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.
Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.
Handle mental health crisis situations in AI coaching safely. Use when implementing crisis detection, safety protocols, emergency escalation, or suicide prevention features. Activates for crisis keywords, safety planning, hotline integration, and risk assessment.
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.
Build and scale partner ecosystems that drive revenue and platform adoption. Use when building partner programs from scratch, tiering partnerships, managing co-marketing, making build-vs-partner decisions, or structuring crawl-walk-run partner deployment.
Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product.
Brainstorm product positioning ideas differentiated from competitors. Identifies top competitors and generates positioning statements with rationale. Use when developing product positioning, differentiating from competitors, or crafting brand positioning strategy.
Generate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.
Take asgard-ai-platform/biz-customer-journey from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.