intended-vs-implemente…
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
$ npx -y skills add phuryn/pm-skills --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 an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
name: customer-journey-map description: "Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey."
Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.
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.
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**:
4. **Identify critical moments**:
5. **Create the journey map table**:
| Stage | Touchpoint | User Action | Emotion | Pain Point | Opportunity | |---|---|---|---|---|---|
6. **Recommend prioritized improvements**:
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.
---
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission…
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating…
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by…
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded…
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team…