Skip to main content
command CX Codex

prioritize-gaps — Claude Code command: what it does, how to install

prioritize-gaps scores customer journey friction points, assigns owners, and creates remediation roadmaps. Helps teams prioritize fixes across onboarding and lifecycle stages.

Apache-2.0 ★ 450 updated 2026-04-03

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

What prioritize-gaps does

The command pulls inputs from journey maps, voice-of-customer data, support tickets, and telemetry flags. It applies a weighting formula across impact, frequency, effort, and strategic fit. This sorts detected friction into quick wins, strategic initiatives, and structural fixes.

Deliverables go beyond a raw table. The workflow assigns accountable teams, prepares backlog entries, and logs an execution schema to .claude/plans/plan-<timestamp>.json. Without customer evidence or existing journey documentation, the scoring engine operates in a vacuum. It hooks into journey-mapping and voice-of-customer skills to keep findings grounded.

A guardrail mechanism sets a retry limit of two attempts for scoring failures. Unassigned high-impact gaps trigger escalation to CX leadership.

What it helps with

  • rank customer journey friction points by effort and impact
  • assign accountable squads and required approvals to fixes
  • cluster remediation work into quick wins and strategic bets
  • generate an audit-ready plan JSON in .claude/plans

Example prompts for the agent

  • /customer-journey-orchestration:prioritize-gaps --persona "IT Director" --scope onboarding --limit 10
  • Analyze onboarding friction for technical leads using /customer-journey-orchestration:prioritize-gaps --persona "IT Director" --scope onboarding
  • Build a remediation roadmap for churn prevention via /customer-journey-orchestration:prioritize-gaps --persona "SMB Owner" --scope retention --limit 5

How to install prioritize-gaps

Manually: put the files in place

.claude/commands/prioritize-gaps.md

Call it with /prioritize-gaps. For all projects use ~/.claude/commands/

Questions about prioritize-gaps

How to install prioritize-gaps in Claude Code?

Place the command markdown file directly into .claude/commands/prioritize-gaps.md within your workspace.

What does prioritize-gaps do?

It aggregates customer friction signals, ranks them with weighted scoring, assigns squad ownership, and builds an action roadmap.

Where does the command output its execution plan?

It saves a structured JSON plan with metrics, dependencies, and owners into .claude/plans/plan-<timestamp>.json.

Source text

prioritize-gaps.md · Apache-2.0
---
name: prioritize-gaps
description: Scores journey friction points, aligns owners, and builds remediation roadmap.
usage: /customer-journey-orchestration:prioritize-gaps --persona "IT Director" --scope onboarding --limit 10
---

# Command: prioritize-gaps

## Inputs
- **persona** – persona/segment for gap analysis.
- **scope** – journey stage or lifecycle slice.
- **limit** – optional cap on number of gaps to surface.
- **criteria** – optional weighting scheme (impact, effort, urgency, customer value).
- **dependencies** – optional notes about systems/teams involved.

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

- **Pattern selection**: Gap prioritization generally runs **pipeline** (aggregation → scoring → owner mapping → roadmap → comms). If scoring + owner mapping can run in parallel (multiple pods), document a **diamond** segment with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with persona/scope, task IDs, weighting criteria, parallel groups, dependency graph (ops, product, eng), error handling, and success metrics (gap closure %, CSAT uplift, time-to-fix).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for instrumentation diffs, Context7 for VOC/support docs, Sequential Thinking for decision tree prompts, Playwright for QA on prototype fixes if required.
- **Guardrails**: Default retry limit = 2 for scoring/owner mapping failures; escalation path = Journey Ops Owner → CX Strategist → CCO/CS leadership.
- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm facilitators, data sources, and deliverables.

## Workflow
1. **Gap Aggregation** – pull journey map findings, VOC insights, support tickets, and telemetry anomalies.
2. **Scoring Engine** – apply weighting (impact × frequency × effort × strategic fit) to rank opportunities.
3. **Owner Mapping** – assign accountable teams, supporting partners, and required approvals.
4. **Roadmap Packaging** – cluster into quick wins, strategic bets, and structural fixes with timelines.
5. **Communication Plan** – generate summary for executives + working teams with next steps.

## Outputs
- Prioritized gap list with scores, owners, and proposed actions.
- Portfolio view (quick wins vs strategic initiatives) with resource estimates.
- Governance-ready backlog entry for each initiative.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `journey-ops-owner` – coordinates resourcing + timelines.
- `journey-mapping` skill – ensures gap definitions align with map standards.
- `voice-of-customer` skill – keeps scoring grounded in customer evidence.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., CX Strategist covering Journey Ops Owner) when resource owners unavailable.
- **Escalation triggers**: if high-impact gaps remain unassigned after two checkpoints or portfolio balance violates guardrails, escalate to CX/Product leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log whenever scoring criteria, owners, or dependencies change to maintain GTM Agents audit parity.

---

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

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set224

The whole set →
define-handoff define-handoff — a command to design lead-to-sales handoff: sets routing rules, response SLAs, and enablement requirements for each sales pod or segment. CX Codex +1 ★ 450repo stars 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 map-journey 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. 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

Project sponsors

Companies that keep this analytics open