Skip to main content
command CX Codex

map-journey — Claude Code command for customer journey mapping

map-journey — a Claude Code command that runs a structured journey mapping workshop, from research compilation to a gap log with assigned owners. Takes persona, scope, and time horizon as inputs.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/map-journey.md
Open on GitHub

What map-journey does

The command /customer-journey-orchestration:map-journey runs in Claude Code with three core flags: --persona for the target segment, --scope for the journey slice (awareness, onboarding, adoption, renewal, or expansion), and --horizon for the analysis window (e.g., 6months, lifecycle). Two optional flags let you specify VOC or telemetry sources via --data_sources and workshop participants via --facilitators.

Execution follows five stages: assembling a discovery packet, running the workshop through stage definition and emotion mapping, injecting VOC quotes and product metrics as an evidence layer, logging friction points with root causes, and producing a final synthesis. Outputs include a journey diagram with touchpoints, KPIs, and owners; a data-backed gap log; and a stakeholder recap with action items. Everything is written to .claude/plans/plan-<timestamp>.json for audit purposes.

The command delegates to the cx-strategist and research-lead agents and the journey-mapping skill from the gtmagents/gtm-agents repository — those agents must be configured for the full workflow to run. If critical gaps have no owner after two checkpoints, an escalation ladder fires: CX Strategist → Journey Ops Owner → CCO/CS leadership.

What it helps with

  • Compile a research and telemetry packet before a journey mapping session
  • Run a multi-stakeholder workshop and assign ownership to every touchpoint
  • Ground journey decisions in VOC quotes and product metrics
  • Log friction points with supporting data and candidate fixes
  • Store a versioned audit trail of workshop outputs in structured JSON

Example prompts for the agent

  • Run an onboarding workshop for the IT Director persona over a 6-month horizon: /customer-journey-orchestration:map-journey --persona "IT Director" --scope "onboarding" --horizon 6months
  • Map the renewal journey for the Enterprise segment pulling from two telemetry sources: `/customer-journey-orchestration:map-journey --persona "Enterprise" --scope "renewal" --horizon lifecycle --data_sources "Intercom,Mixpanel"`
  • Add CX and Product stakeholders as workshop facilitators: `/customer-journey-orchestration:map-journey --persona "SMB Owner" --scope "adoption" --horizon 6months --facilitators "cx-lead,product-manager"`

How to install map-journey

Manually: put the files in place

.claude/commands/map-journey.md

Call it with /map-journey. For all projects use ~/.claude/commands/

Questions about map-journey

How do I install map-journey in Claude Code?

Place the command file at .claude/commands/map-journey.md in your project root. The command then becomes available as /customer-journey-orchestration:map-journey.

What does the map-journey command do?

It guides a team through a full journey mapping workshop: research collection, stage and touchpoint definition, emotion mapping, evidence injection from VOC and metrics, gap logging, and a final blueprint with action items.

Which agents does map-journey require?

The command calls cx-strategist, research-lead, and the journey-mapping skill from the gtmagents/gtm-agents repository. Without those agents configured, parts of the workflow will not execute.

Source text

map-journey.md · Apache-2.0
---
name: map-journey
description: Facilitates end-to-end journey mapping workshops with data-backed insights and ownership plans.
usage: /customer-journey-orchestration:map-journey --persona "IT Director" --scope "onboarding" --horizon 6months
---

# Command: map-journey

## Inputs
- **persona** – target persona or segment.
- **scope** – journey slice (awareness, onboarding, adoption, renewal, expansion).
- **horizon** – time window to analyze (e.g., 6months, lifecycle).
- **data_sources** – optional list of VOC/telemetry sources to emphasize.
- **facilitators** – optional list of stakeholders joining workshops.

### GTM Agents Pattern & Plan Checklist
> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Journey mapping typically runs **pipeline** (discovery → workshop → evidence → gaps → synthesis). If workshop activities can split (e.g., persona + channel subgroups), log a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing persona, scope, task IDs, parallel groups, dependency graph (research, CX ops, product), error handling, and success metrics (gap closure %, NPS uplift, time-to-resolution).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for instrumentation diffs, Context7 for VOC/support docs, Sequential Thinking for facilitation prompts, Playwright for QA on journey prototypes if needed.
- **Guardrails**: Default retry limit = 2 for evidence gaps or facilitation blockers; escalation ladder = CX Strategist → Journey Ops Owner → CCO/CS leadership.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm facilitators, dependencies, and deliverables.

## Workflow
1. **Discovery Packet** – compile research, telemetry, and existing maps for the selected persona/scope.
2. **Workshop Flow** – guide stakeholders through stage definition, touchpoint inventory, emotion mapping, and ownership assignment.
3. **Evidence Layer** – inject VOC quotes, product metrics, and support data to ground decisions.
4. **Gap Logging** – capture friction points, root causes, and potential solutions.
5. **Synthesis** – produce journey blueprint, highlight quick wins, and queue items for prioritization.

## Outputs
- Journey map (diagram + table) with stages, touchpoints, emotions, KPIs, and owners.
- Gap log referencing supporting data and potential solutions.
- Stakeholder recap with action items and next steps.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `cx-strategist` – leads facilitation and synthesis.
- `journey-mapping` skill – provides templates/checklists.
- `research-lead` – injects VOC evidence.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Journey Ops Owner covering CX Strategist) when facilitators unavailable.
- **Escalation triggers**: if critical gaps lack owners after two checkpoints or evidence quality falls below guardrails, escalate to CX + Product leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log when scope, facilitators, or data sources change to keep audit alignment with GTM Agents procedures.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
monitor-personalization monitor-personalization audits personalization campaigns, tracks experiment outcomes, and flags consent violations across user segments. CX Codex +1 ★ 450repo stars editorial-ops editorial-ops is a Claude Code skill that plans multi-channel editorial calendars and coordinates GTM content production from ideation through distribution, with KPI guardrails set before assets ship. CX Codex +1 ★ 450repo stars measure-engagement measure-engagement pulls community health metrics, sentiment, and experiment results into one report with a prioritized action list. Use it when you need to see what is happening in a community and what to do about it. CX Codex +1 ★ 450repo stars prioritize-gaps prioritize-gaps scores customer journey friction points, assigns owners, and creates remediation roadmaps. Helps teams prioritize fixes across onboarding and lifecycle stages. CX Codex +1 ★ 450repo stars plan-community-calendar plan-community-calendar builds a community programming calendar spanning 8 weeks or a quarter, with themes, formats, owners and dependencies. CX Codex +1 ★ 450repo stars run-survey run-survey orchestrates customer surveys with target sampling, structured question banks, and distribution steps. CX Codex +1 ★ 450repo stars configure-rules The configure-rules command takes personalization rules through data checks, decision setup, variant mapping, QA, and deployment. Use it to prepare changes for web and in-app channels. CX Codex +1 ★ 450repo stars forecast-renewals forecast-renewals — a command that builds segmented renewal forecasts with account health signals, variance analysis, and executive reporting. Combines ARR, NRR, and risk data into a single view. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open