Skip to main content
command CX Codex

inspect-pipeline-levers — Claude Code command: setup and features

inspect-pipeline-levers diagnoses sales pipeline coverage, conversion velocity, and deal friction directly inside CRM data.

Apache-2.0 ★ 450 updated 2026-04-03

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

What inspect-pipeline-levers does

The command pulls pipeline tables, enrichment data, and coaching notes out of your CRM. Next, it splits records by product, region, or persona to calculate stage-to-stage transition times. At-risk opportunities get flagged alongside concrete next steps.

Execution relies on specialized agents and skills: pipeline-analytics-lead runs the core diagnostics, revenue-intelligence-director builds the executive memo, while deal-quality-model and cohort-analysis inspect hygiene signals against historical cohorts.

Without direct access to CRM records and deal notes, the underlying agents cannot compute stage leakage or velocity metrics.

What it helps with

  • diagnose conversion leaks across pipeline stages
  • identify stuck enterprise opportunities before quarter close
  • compare segment win rates against historical cohort benchmarks
  • generate pipeline risk memos for sales leadership

Example prompts for the agent

  • /revenue-analytics:inspect-pipeline-levers --stage commit --segments enterprise --window 30d --output dashboard
  • /revenue-analytics:inspect-pipeline-levers --stage qualify --window quarter --output memo
  • /revenue-analytics:inspect-pipeline-levers --stage pipeline --metrics coverage,slip_rate --output slack

How to install inspect-pipeline-levers

Manually: put the files in place

.claude/commands/inspect-pipeline-levers.md

Call it with /inspect-pipeline-levers. For all projects use ~/.claude/commands/

Questions about inspect-pipeline-levers

How to install inspect-pipeline-levers in Claude Code?

Place the command specification file into .claude/commands/inspect-pipeline-levers.md in your repository.

What output formats are supported?

The command accepts dashboard, memo, csv, or slack through the --output parameter.

Which sub-agents and skills are invoked?

It orchestrates pipeline-analytics-lead and revenue-intelligence-director, plus the deal-quality-model and cohort-analysis skills.

Source text

inspect-pipeline-levers.md · Apache-2.0
---
name: inspect-pipeline-levers
description: Diagnoses pipeline coverage, conversion velocity, and stuck deal patterns.
usage: /revenue-analytics:inspect-pipeline-levers --stage commit --segments enterprise --window 30d --output dashboard
---

# Command: inspect-pipeline-levers

## Inputs
- **stage** – stage or grouping to inspect (create, qualify, pipeline, best-case, commit, closed).
- **segments** – persona, region, product, or team filters.
- **window** – lookback window (7d, 30d, quarter, custom).
- **metrics** – focus metrics (coverage, velocity, win_rate, asp, slip_rate).
- **output** – dashboard | memo | csv | slack.

## Workflow
1. **Data Extraction** – pull CRM pipeline tables plus enrichment fields and coach notes.
2. **Segmentation** – slice by requested segments, highlight outliers vs benchmark.
3. **Leakage & Velocity** – compute stage-to-stage conversion, cycle time, and stuck counts.
4. **Opportunity Drilldown** – flag top stuck/at-risk deals with context + next steps.
5. **Packaging & Alerts** – produce requested view plus Slack/Email summary for owners.

## Outputs
- Pipeline lever dashboard with stage conversion, velocity, and coverage deltas.
- Stuck/at-risk deal list with recommended plays.
- Summary memo highlighting root causes + action plan.

## Agent/Skill Invocations
- `pipeline-analytics-lead` – runs diagnostics + highlights at-risk segments.
- `revenue-intelligence-director` – frames executive-ready narrative.
- `deal-quality-model` skill – evaluates opportunity hygiene + win signals.
- `cohort-analysis` skill – benchmarks performance vs historical cohorts.

---

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

Similar slash commands

All slash commands for Finance and business →
sales-pipeline-coverage-modeling Maya-Beth Finotti sales-pipeline-coverage-modeling models pipeline coverage ratios against sales quota using historical conversion rates. Helps RevOps and sales leaders identify pipeline gaps and plan deals. CX Codex +1 34,600installs pipeline-stage-definition-audit Maya-Beth Finotti pipeline-stage-definition-audit is a skill that checks whether sales pipeline stages reflect buyer actions or seller activity. It reports ranked findings, revised exit criteria, and a migration plan. CX Codex +1 27,600installs pipeline-review official anthropics pipeline-review evaluates stage-by-stage pipeline health, aging deals, and coverage from CRM records or file exports. Handy for weekly sales reviews. CX Codex +1 2,900installs pipeline-health-analyzer OneWave-AI pipeline-health-analyzer reads a deal export, flags stalled and at-risk opportunities, scores close probability and prescribes next actions. CX Codex +1 339installs team-pipeline official Anthropic The team-pipeline Claude Code skill rolls up a team’s pipeline by rep and stage. Ask for a team forecast, pipeline review prep, or areas where reps need coaching. CX Codex +1 ★ 36,654repo stars deal-pipeline-reconstructor Mario Aldayuz / Littlebird The deal-pipeline-reconstructor skill assembles your deals from messages, calls and notes into a structured board. Sellers without a CRM can see what stage each opportunity is at, what evidence supports it, and which ones have gone quiet. CX Codex +1 ★ 96repo stars

From the same set224

The whole set →
synthesize-insights synthesize-insights turns scattered customer feedback and usage numbers into one brief for leadership: themes, quotes, metrics and owners. CX Codex +1 ★ 450repo stars audit-provider-health audit-provider-health assesses enrichment provider latency, quality, and credit spend. Useful for reviewing supplier SLAs and cleaning up data pipelines. CX Codex +1 ★ 450repo stars case-studies case-studies — a Claude Code skill that structures customer stories using the CHIC framework: Challenge, Hypothesis, Implementation, Change. Runs whenever sales needs proof points or marketing is building a social-proof campaign. CX Codex +1 ★ 450repo stars build-capacity-plan build-capacity-plan turns a revenue target into headcount, quota and productivity scenarios for base, upside and downside cases, with a hiring plan attached. CX Codex +1 ★ 450repo stars activate-program activate-program is a Claude Code command that turns a candidate roster into a live advocacy program by assigning owners, triggering approvals, and starting outreach tracking. CX Codex +1 ★ 450repo stars operationalize-pql-routing operationalize-pql-routing turns product signals into a scoring and routing plan for product-qualified leads, then hands back a spec, an automation checklist and a follow-up playbook. CX Codex +1 ★ 450repo stars build-value-narrative build-value-narrative — a Claude Code command that generates ROI/TCO models, executive storylines, and proof appendices for complex deals. Runs against a named opportunity with industry, scenarios, and target exec roles as inputs. CX Codex +1 ★ 450repo stars launch-program The launch-program command maps out an enablement program launch, from objectives and milestones to communications, training, and certification. Use it to plan a new team initiative. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open