Customer Journey Map
Map how your target persona discovers, evaluates, adopts, and advocates for your product so discovery and GTM decisions stay grounded in real behavior.
Overview
Customer Journey Map is an agent skill most often used in Validate (also Idea research, Grow lifecycle) that produces a persona-aligned journey table from awareness through loyalty.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill customer-journey-mapWhat is this skill?
- Structured table across Awareness → Loyalty with customer actions and touchpoints per stage
- Persona + objectives block so maps tie to measurable adoption and activation goals
- Dogfooding example models quality bar using the PM skills repo itself
- Reusable markdown artifact for planning, positioning, and internal alignment
- Works for B2B SaaS-style adoption funnels and open-source or skill-library GTM
- Five journey columns: Awareness, Consideration, Decision, Service, Loyalty
Adoption & trust: 1.3k installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know your product idea but cannot articulate how buyers actually discover it, stall, or convert across stages.
Who is it for?
Solo builders or indie SaaS founders who want a PM-grade journey artifact before committing to landing pages, onboarding, or distribution experiments.
Skip if: Teams that already maintain a validated journey map tied to live analytics—skip unless you are refreshing positioning or entering a new segment.
When should I use this skill?
You need a structured customer journey map with persona, objectives, and per-stage actions and touchpoints for a real product.
What do I get? / Deliverables
You leave with a markdown customer journey map linking persona objectives, actions, and touchpoints per stage, ready to inform scope, messaging, and activation metrics.
- Markdown customer journey map table with stages, actions, and touchpoints
- Persona and measurable objectives section
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Journey mapping is the canonical shelf in Validate because solo builders use it to prove they understand the buyer path before committing to a full build or launch plan. Scope subphase fits when you are defining who the customer is, what they do at each stage, and which touchpoints matter—directly informing MVP scope and messaging.
Where it fits
Model how an AI-forward PM lead first hears about your skill library on LinkedIn versus GitHub search before you pick channels.
Align MVP scope to the Consideration and Decision actions so the first clone-and-run experience matches what the map promises.
Refine Service and Loyalty rows to reduce churn and encourage issues or PRs from power users.
How it compares
Use for structured journey tables and persona objectives, not as a substitute for analytics dashboards or session replay tools.
Common Questions / FAQ
Who is customer-journey-map for?
Indie and solo builders shipping SaaS or content products who want practical PM frameworks inside Claude, Codex, or Cursor—not enterprise workshop facilitation only.
When should I use customer-journey-map?
During Validate scope when defining MVP and messaging; in Idea audience research when modeling how a segment hears about you; and in Grow lifecycle when improving activation, service, and advocacy touchpoints.
Is customer-journey-map safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and the source repo before running it in a repo with secrets.
SKILL.md
READMESKILL.md - Customer Journey Map
# 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 ``` # Customer Journey Map Example ## Example: B2B SaaS Product ```markdown ## Customer Journey Map: Manager Mike (Product Management Tool) ### Persona - Manager