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
.claude/commands/prioritize-gaps.mdWhat 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.mdCall it with /prioritize-gaps. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/prioritize-gaps.mdCall it with /prompts:prioritize-gaps. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/prioritize-gaps.prompt.mdManually: put the files in place
.gemini/commands/prioritize-gaps.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
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