autodoc-agent-kit 1.0.0

package/src/modules/product/skills/customer-journey-map/SKILL.md

@@ -0,0 +1,346 @@
+---
+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"
+---
+
+
+## Purpose
+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.
+
+## Key Concepts
+
+### The Customer Journey Mapping Framework
+Adapted from NNGroup's framework and Carnegie Mellon's PM curriculum, a customer journey map documents:
+
+**Horizontal structure (stages):**
+- **Awareness:** Customer first learns about your brand
+- **Consideration:** Customer evaluates your offering
+- **Decision:** Customer makes a purchase
+- **Service:** Customer uses the product/service post-purchase
+- **Loyalty:** Customer becomes a repeat buyer and advocate
+
+**Vertical structure (for each stage):**
+- **Customer Actions:** What customers do
+- **Touchpoints:** Where/how they interact with your brand
+- **Customer Experience:** Emotions and thoughts
+- **KPIs:** Metrics to measure success
+- **Business Goals:** What you're trying to achieve
+- **Teams Involved:** Who owns this stage
+
+### Why This Works
+- **Empathy-driven:** Centers on customer emotions, not just actions
+- **Cross-functional alignment:** Shows which teams affect which stages
+- **Metric-focused:** Ties customer experience to measurable outcomes
+- **Gap identification:** Makes pain points and opportunities visible
+- **Actionable:** Clear KPIs and goals enable prioritization
+
+### Anti-Patterns (What This Is NOT)
+- **Not a user story map:** Journey maps are broader (all touchpoints, not just product use)
+- **Not a service blueprint:** Less detailed on internal processes, more focused on customer experience
+- **Not static:** Journey maps evolve as customer behavior changes
+
+### When to Use This
+- Understanding customer experience across all touchpoints (not just product)
+- Aligning cross-functional teams (marketing, sales, product, support)
+- Identifying pain points and prioritizing improvements
+- Onboarding new team members to customer perspective
+- Auditing the end-to-end customer experience
+
+### When NOT to Use This
+- For deep product-specific workflows (use story mapping instead)
+- Before defining personas (need to know who you're mapping)
+- As a one-time exercise (journey maps require ongoing updates)
+
+---
+
+## Application
+
+Use `template.md` for the full fill-in structure.
+
+### Step 1: Prepare Prerequisites
+
+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.
+
+---
+
+### Step 2: Set Clear Objectives
+
+Define what you want to achieve:
+
+```markdown
+## 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:**
+- **Specific:** Not "understand customers" but "identify drop-off causes in Consideration stage"
+- **Actionable:** Results should inform decisions, not just document observations
+
+---
+
+### Step 3: Choose a Buyer Persona
+
+Select one persona to focus on (create separate maps for each persona):
+
+```markdown
+## 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.
+
+---
+
+### Step 4: Map Each Stage
+
+For each stage (Awareness, Consideration, Decision, Service, Loyalty), document:
+
+#### Customer Actions
+What customers do at this stage:
+
+```markdown
+### 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:**
+- **Observable:** You can see or measure this action
+- **Specific:** Not "research products" but "Google 'best roadmap software' and read comparison articles"
+
+---
+
+#### Touchpoints
+Where/how customers interact with your brand:
+
+```markdown
+**Touchpoints:**
+- [Touchpoint 1: e.g., "LinkedIn Ads"]
+- [Touchpoint 2: e.g., "Word-of-mouth at PM conferences"]
+- [Touchpoint 3: e.g., "Google organic search results"]
+- [Touchpoint 4: e.g., "Review sites (G2, Capterra)"]
+```
+
+**Quality checks:**
+- **Comprehensive:** Include both digital and physical touchpoints
+- **Specific:** Not "social media" but "LinkedIn Ads," "Twitter mentions," etc.
+
+---
+
+#### Customer Experience
+Emotions and thoughts customers have:
+
+```markdown
+**Customer Experience:**
+- [Emotion 1: e.g., "Curious but skeptical—'Is this actually better than spreadsheets?'"]
+- [Emotion 2: e.g., "Overwhelmed by options—'Too many tools, how do I choose?'"]
+- [Emotion 3: e.g., "Hopeful but cautious—'Could this save me time?'"]
+```
+
+**Quality checks:**
+- **Authentic:** Use customer quotes from research when possible
+- **Emotional:** Capture feelings, not just thoughts
+- **Specific:** Not "interested" but "curious but skeptical—worried about setup time"
+
+---
+
+#### KPIs
+Key performance indicators for this stage:
+
+```markdown
+**KPIs:**
+- [KPI 1: e.g., "Brand awareness (measured via surveys)"]
+- [KPI 2: e.g., "LinkedIn ad impressions: 100k/month"]
+- [KPI 3: e.g., "Organic search traffic: 5k visitors/month"]
+- [KPI 4: e.g., "G2 review views: 2k/month"]
+```
+
+**Quality checks:**
+- **Measurable:** Can you track this?
+- **Stage-appropriate:** Awareness KPIs differ from Decision KPIs
+
+---
+
+#### Business Goals
+What you're trying to achieve at this stage:
+
+```markdown
+**Business Goals:**
+- [Goal 1: e.g., "Increase brand awareness among PMs at B2B SaaS companies"]
+- [Goal 2: e.g., "Generate 500 qualified leads/month"]
+- [Goal 3: e.g., "Position as top 3 roadmap tool in G2 rankings"]
+```
+
+**Quality checks:**
+- **Outcome-focused:** Not "run ads" but "increase brand awareness"
+- **Aligned with stage:** Don't expect conversions at Awareness stage
+
+---
+
+#### Teams Involved
+Who owns this stage:
+
+```markdown
+**Teams Involved:**
+- [Team 1: e.g., "Marketing (ad campaigns, SEO)"]
+- [Team 2: e.g., "Content (blog posts, comparison guides)"]
+- [Team 3: e.g., "Customer Success (case studies, testimonials)"]
+```
+
+**Quality checks:**
+- **Cross-functional:** Multiple teams usually touch each stage
+- **Specific roles:** Not just "marketing" but "marketing (ad campaigns, SEO)"
+
+---
+
+### Step 5: Visualize the Map
+
+Create a table or visual diagram:
+
+| **Stage** | **Awareness** | **Consideration** | **Decision** | **Service** | **Loyalty** |
+|-----------|---------------|-------------------|--------------|-------------|-------------|
+| **Customer Actions** | See ad, hear from peers, Google search | Compare features, read reviews, request demo | Free trial signup, test with real data, evaluate ROI | Onboard team, build first roadmap, integrate with Jira | Use daily, recommend to peers, share wins on LinkedIn |
+| **Touchpoints** | LinkedIn Ads, conferences, Google, review sites | Website, demo calls, sales emails | Product (free trial), onboarding emails | Product, support chat, knowledge base | Product, community forums, customer success check-ins |
+| **Customer Experience** | Curious but skeptical | Excited but overwhelmed by options | Anxious about setup time, hopeful about time savings | Relieved if easy, frustrated if complex | Satisfied and confident, proud of wins |
+| **KPIs** | Impressions: 100k/month, traffic: 5k/month | Demo requests: 100/month, trial signups: 50/month | Conversion rate: 20%, time-to-value: <2 hours | Activation rate: 70%, support ticket volume | Retention rate: 85%, NPS: 50, referral rate: 15% |
+| **Business Goals** | Increase brand awareness, generate 500 leads/month | Improve lead quality, reduce sales cycle to 30 days | Increase trial-to-paid conversion, optimize onboarding | Reduce churn, improve activation, minimize support costs | Increase LTV, generate referrals, upsell premium features |
+| **Teams Involved** | Marketing, Content | Marketing, Sales, Product | Sales, Product, Onboarding | Product, Support, Customer Success | Product, Customer Success, Marketing |
+
+---
+
+### Step 6: Analyze and Prioritize
+
+Review the map and ask:
+1. **Where are the biggest pain points?** (Look for negative emotions + high drop-off rates)
+2. **Which stages have the weakest KPIs?** (Prioritize low-performing stages)
+3. **Are teams aligned?** (Do teams understand their role in each stage?)
+4. **What opportunities exist?** (Where can small improvements create big impact?)
+
+**Prioritization criteria:**
+- **Impact:** How much would fixing this improve the customer experience?
+- **Feasibility:** How easy is this to fix?
+- **Alignment:** Does this support business goals?
+
+---
+
+### Step 7: Test and Refine
+
+- **Update regularly:** Customer behavior changes—revisit the map quarterly
+- **Validate with data:** Use analytics, surveys, and customer interviews to confirm assumptions
+- **Track improvements:** After making changes, measure impact on KPIs
+
+---
+
+## Examples
+
+See `examples/sample.md` for a full customer journey map example.
+See `examples/meta-product-manager-skills.md` for a meta dogfooding example mapping this repository's own customer journey.
+
+Mini example excerpt:
+
+```markdown
+| **Stage** | **Awareness** | **Consideration** | **Decision** |
+| **Customer Actions** | Sees LinkedIn ad | Compares on G2 | Starts free trial |
+| **Customer Experience** | Curious but skeptical | Overwhelmed | Anxious about setup |
+```
+
+---
+
+## Common Pitfalls
+
+### Pitfall 1: Generic Emotions
+**Symptom:** "Customer feels happy" or "Customer is satisfied"
+
+**Consequence:** No insight into *why* they feel that way or what to improve.
+
+**Fix:** Be specific: "Relieved that setup took 30 minutes, not 3 hours as feared."
+
+---
+
+### Pitfall 2: Missing Touchpoints
+**Symptom:** Only documenting digital touchpoints (website, app)
+
+**Consequence:** Miss offline interactions (conferences, word-of-mouth, support calls).
+
+**Fix:** Include all touchpoints: physical, digital, human, and automated.
+
+---
+
+### Pitfall 3: Internal Perspective
+**Symptom:** Mapping what *you* want customers to do, not what they *actually* do
+
+**Consequence:** Journey map reflects wishful thinking, not reality.
+
+**Fix:** Validate with customer research, analytics, and support tickets.
+
+---
+
+### Pitfall 4: No KPIs or Goals
+**Symptom:** Journey map has actions and emotions but no metrics or business objectives
+
+**Consequence:** No way to measure success or prioritize improvements.
+
+**Fix:** Add KPIs and business goals for each stage. Make them measurable.
+
+---
+
+### Pitfall 5: One-and-Done Exercise
+**Symptom:** Journey map created once, never updated
+
+**Consequence:** Map becomes outdated as customer behavior evolves.
+
+**Fix:** Review quarterly. Update based on new data, product changes, or market shifts.
+
+---
+
+## References
+
+### Related Skills
+- `skills/proto-persona/SKILL.md` — Defines the persona for the journey map
+- `skills/jobs-to-be-done/SKILL.md` — Informs customer actions and goals
+- `skills/problem-statement/SKILL.md` — Identifies pain points at each stage
+- `skills/user-story-mapping/SKILL.md` — Complementary (story mapping focuses on product usage, journey mapping covers all touchpoints)
+
+### External Frameworks
+- NNGroup, *Customer Journey Mapping* (2016) — Foundational framework
+- Carnegie Mellon University, *Product Management Curriculum* — Academic approach
+- Chris Risdon & Patrick Quattlebaum, *Orchestrating Experiences* (2018) — Journey mapping for service design
+
+### Dean's Work
+- Customer Journey Mapping Prompt Template (adapted from NNGroup and CMU frameworks)
+
+### Provenance
+- Adapted from `prompts/customer-journey-mapping-prompt-template.md` in the `https://github.com/deanpeters/product-manager-prompts` repo.
+
+---
+
+**Skill type:** Component
+**Suggested filename:** `customer-journey-map.md`
+**Suggested placement:** `/skills/components/`
+**Dependencies:** References `skills/proto-persona/SKILL.md`, `skills/jobs-to-be-done/SKILL.md`, `skills/problem-statement/SKILL.md`

package/src/modules/product/skills/customer-journey-map/examples/meta-product-manager-skills.md

@@ -0,0 +1,40 @@
+# Customer Journey Map Example
+
+## Meta Dogfooding Example: Product Manager Skills Repo
+
+This example intentionally maps our own repository journey to model the operating principle of dogfooding: we use the same PM artifacts and quality bar we ask others to use.
+
+```markdown
+## Customer Journey Map: AI-Forward PM Lead (Product Manager Skills)
+
+### Product
+Product Manager Skills (open-source PM skill library for agentic workflows in Claude/Codex)
+
+### Persona
+- AI-Forward PM Lead: PM leader at a B2B SaaS company (20-300 employees), accountable for faster discovery/delivery, skeptical of AI hype, values practical frameworks and reusable workflows
+
+### Objectives
+- Increase qualified adoption of PM skills in real product workflows
+- Improve first-week activation from discovery to successful skill usage
+- Increase repeat usage and contribution behavior
+
+| **Stage** | **Awareness** | **Consideration** | **Decision** | **Service** | **Loyalty** |
+|---|---|---|---|---|---|
+| **Customer Actions** | Sees LinkedIn/Substack post, hears about repo from peers, searches for PM skills for Claude/Codex | Reads README, scans skill catalog, compares with prompt libraries, checks docs | Clones repo, selects 1-2 skills, runs first guided flow, evaluates output quality | Uses multiple skills in planning/discovery cycles, adapts outputs, shares internally | Reuses as default PM operating layer, recommends to peers, opens issues/PRs |
+| **Touchpoints** | LinkedIn posts, Substack, GitHub repo/search, community mentions | README, CLAUDE.md, usage docs, individual SKILL.md files | Terminal/Codex/Claude session, skill files, helper scripts, quickstart docs | Skill workflows, scripts, docs, release notes, commit history | GitHub issues/PRs, release notes, docs updates, announcements |
+| **Customer Experience** | Curious but skeptical: "Is this practical or just prompt theater?" | Interested but overloaded: "Which skill should I use first?" | Hopeful but anxious: "Will this work in my real context?" | Relieved when outputs are reusable; frustrated if behavior is inconsistent | Confident and invested: "This gives my team a repeatable edge." |
+| **KPIs** | GitHub page views, unique visitors, referral source mix, star rate per visitor | README-to-doc click-through, time on docs, skill page opens, first install intent | First-run success rate, time-to-first-usable-output, setup drop-off, return within 48h | Weekly active users (proxy), multi-skill usage rate, workflow completion rate, issue rate on broken patterns | Repeat contributor count, PR volume/quality, referral traffic, retention of active users |
+| **Business Goals** | Reach qualified PM/PMM/Founder audiences, position as practical and agent-ready | Reduce cognitive load, help users pick the right first skill quickly | Minimize setup friction, prove value in first session | Maintain consistent quality across skills, increase workflow-level adoption | Build contributor flywheel and trust through consistency |
+| **Teams Involved** | Content/author, community, maintainers | Maintainers, doc owners, skill authors | Maintainers, contributors, tooling/script maintainers | Skill authors, reviewers, maintainers | Core maintainers, contributors, community advocates |
+
+### Analysis
+**Top 3 Priority Opportunities:**
+1. First-skill onboarding path: add a "Start Here (15 min)" flow mapping persona to first 3 recommended skills
+2. Consistency guardrails: keep shared facilitation rules centralized and auto-checked for all linked skills
+3. Activation instrumentation: define lightweight metrics for first-run success and multi-skill adoption
+
+### Assumptions to Validate
+1. Primary persona is PM leads at B2B SaaS teams
+2. Most discovery traffic starts from GitHub plus social content
+3. Biggest friction is "which skill first?" plus cross-skill consistency
+```

package/src/modules/product/skills/customer-journey-map/examples/sample.md

@@ -0,0 +1,33 @@
+# Customer Journey Map Example
+
+## Example: B2B SaaS Product
+
+```markdown
+## Customer Journey Map: Manager Mike (Product Management Tool)
+
+### Persona
+- Manager Mike: 35-42, Director of Product at mid-sized B2B SaaS, struggles with data-driven prioritization, values time savings
+
+### Objectives
+- Identify top 3 drop-off points between stages
+- Align marketing, sales, and product on customer motivations
+- Reduce time-to-activation from 4 hours to 2 hours
+
+| **Stage** | **Awareness** | **Consideration** | **Decision** | **Service** | **Loyalty** |
+|---|---|---|---|---|---|
+| **Customer Actions** | Sees LinkedIn ad, hears from PM peer, Googles "roadmap software" | Compares features on G2, reads blog posts, requests demo | Signs up for free trial, tests with real data | Onboards team, builds first roadmap, integrates with Jira | Uses daily, recommends to peers, shares roadmap wins on LinkedIn |
+| **Touchpoints** | LinkedIn Ads, PM conferences, Google organic search, G2 | Website, demo calls, sales emails, G2 reviews | Free trial product, onboarding emails, setup wizard | Product, support chat, knowledge base, video tutorials | Product, community forum, CSM check-ins, case study participation |
+| **Customer Experience** | Curious but skeptical: "Is this better than spreadsheets?" | Excited but overwhelmed: "Too many options, how do I choose?" | Anxious: "Will setup take all weekend?" | Relieved: "This was easier than expected!" | Confident: "My roadmaps are finally data-driven." |
+| **KPIs** | Ad impressions: 100k/month, organic traffic: 5k/month, G2 views: 2k/month | Demo requests: 100/month, trial signups: 50/month | Trial-to-paid conversion: 20%, time-to-first-roadmap: 2 hours | Activation rate: 70%, support tickets: 2/user, onboarding NPS: 8 | Retention: 85%, NPS: 50, referrals: 15%, upsell rate: 10% |
+| **Business Goals** | Increase brand awareness, generate 500 qualified leads/month | Improve lead quality, reduce sales cycle to 30 days | Increase conversion from 20% to 25%, reduce time-to-value | Reduce churn from 15% to 10%, increase activation to 80% | Increase LTV by 20%, generate 50 referrals/quarter |
+| **Teams Involved** | Marketing (ads, SEO), Content (blog) | Marketing, Sales, Product (demos) | Sales, Product (trial), Onboarding | Product, Support, Customer Success | Customer Success, Marketing (case studies), Product (features) |
+
+### Analysis
+**Top Pain Points:**
+1. Consideration stage drop-off: 100 demo requests → 50 trial signups (50% drop-off)
+2. Decision stage anxiety: "Will setup take all weekend?"
+3. Service stage activation: Only 70% activate
+
+**Opportunities:**
+1. Loyalty stage: High NPS (50) but low referral rate (15%)
+```

package/src/modules/product/skills/customer-journey-map/template.md

@@ -0,0 +1,28 @@
+# Customer Journey Map Template
+
+Use this template to map customer stages, actions, touchpoints, emotions, KPIs, goals, and teams.
+
+## Provenance
+Adapted from `prompts/customer-journey-mapping-prompt-template.md` in the `https://github.com/deanpeters/product-manager-prompts` repo.
+
+## Template
+```markdown
+## Customer Journey Map
+
+### Persona
+- [Persona name and brief description]
+
+### Objectives
+- [Objective 1]
+- [Objective 2]
+- [Objective 3]
+
+| **Stage** | **Awareness** | **Consideration** | **Decision** | **Service** | **Loyalty** |
+|---|---|---|---|---|---|
+| **Customer Actions** | [Actions] | [Actions] | [Actions] | [Actions] | [Actions] |
+| **Touchpoints** | [Touchpoints] | [Touchpoints] | [Touchpoints] | [Touchpoints] | [Touchpoints] |
+| **Customer Experience** | [Emotions/thoughts] | [Emotions/thoughts] | [Emotions/thoughts] | [Emotions/thoughts] | [Emotions/thoughts] |
+| **KPIs** | [KPIs] | [KPIs] | [KPIs] | [KPIs] | [KPIs] |
+| **Business Goals** | [Goals] | [Goals] | [Goals] | [Goals] | [Goals] |
+| **Teams Involved** | [Teams] | [Teams] | [Teams] | [Teams] | [Teams] |
+```