brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.
$ npx -y skills add getcrew44/crew44 --skill customer-journey-map --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/customer-journey-mapContext preview
The summary Claude sees to decide when to auto-load this skill.
Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.
name: customer-journey-map description: Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow. intent: >- Create a comprehensive customer journey map that visualizes how customers interact with your brand across all stages—from awareness to loyalty—documenting their actions, touchpoints, emotions, KPIs, business goals, and teams involved at each stage. Use this to identify pain points, align cross-functional teams, and systematically improve the customer experience to achieve business objectives. type: component theme: workshops-facilitation best_for: - "Mapping the full customer experience across all touchpoints" - "Aligning cross-functional teams on the end-to-end customer journey" - "Identifying pain points and opportunities by stage with measurable KPIs" scenarios: - "I need to map the customer journey for our B2B SaaS onboarding experience from signup to first value" - "Create a journey map for a PM leader evaluating our skills repo — from discovery through loyalty" estimated_time: "20-30 min"
Create a comprehensive customer journey map that visualizes how customers interact with your brand across all stages—from awareness to loyalty—documenting their actions, touchpoints, emotions, KPIs, business goals, and teams involved at each stage. Use this to identify pain points, align cross-functional teams, and systematically improve the customer experience to achieve business objectives.
This is not a user flow diagram—it's a strategic artifact that combines customer empathy with business metrics to drive actionable improvements.
Adapted from NNGroup's framework and Carnegie Mellon's PM curriculum, a customer journey map documents:
**Horizontal structure (stages):**
**Vertical structure (for each stage):**
---
Use `template.md` for the full fill-in structure.
Before mapping, ensure you have: 1. **Key stakeholders:** Marketing, sales, product, customer service representatives 2. **Buyer personas:** Detailed personas with demographics, psychographics, goals, challenges (reference `skills/proto-persona/SKILL.md`) 3. **Defined stages:** Main stages of your buying process (typically: Awareness, Consideration, Decision, Service, Loyalty) 4. **Touchpoint inventory:** All places customers interact with your brand (website, social, email, store, support, etc.)
**If missing:** Run discovery interviews, persona definition work, or touchpoint audits first.
---
Define what you want to achieve:
## Objectives - [Goal 1: e.g., "Identify top 3 pain points causing drop-off between Awareness and Consideration"] - [Goal 2: e.g., "Align marketing and sales on customer motivations at each stage"] - [Goal 3: e.g., "Understand emotional journey to inform messaging strategy"]
**Quality checks:**
---
Select one persona to focus on (create separate maps for each persona):
## Persona - [Persona name and brief description] - [Example: "Manager Mike: 35-42, Director of Product at mid-sized B2B SaaS, struggles with data-driven prioritization, values time savings over feature depth"]
**Why one persona per map:** Different personas have different journeys. Mixing them creates confusion.
---
For each stage (Awareness, Consideration, Decision, Service, Loyalty), document:
What customers do at this stage:
### Stage: [Stage Name, e.g., Awareness] **Customer Actions:** - [Action 1: e.g., "See LinkedIn ad about product management tools"] - [Action 2: e.g., "Hear about tool from PM peer at conference"] - [Action 3: e.g., "Google 'best product roadmap software'"]
**Quality checks:**
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes