revops-diagnostic

Diagnose B2B revenue system constraints using IFA and Six Stages of Check workflows.

40|18|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/NEON-Rutger/B2B-revops-skills --skill revops-diagnostic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revops-diagnostic
Source: https://github.com/NEON-Rutger/B2B-revops-skills/tree/main/revops-diagnostic
Command: npx skills add https://github.com/NEON-Rutger/B2B-revops-skills --skill revops-diagnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you stop guessing when pipeline, forecasts, rep performance, churn, or cross-functional chaos show up, by identifying the true constraint in your B2B revenue system and the root causes behind the symptoms.

Core Features & Use Cases

  • System-layer diagnosis (Governance → Enablement → ICP Value Loops): Turns “what’s wrong” into a structured check of where steering, infrastructure, or feedback loops are failing.
  • IFA and Six Stages of Check: Pinpoints which link is weakest (Information, Focus, or Action) and whether the issue is in Purpose/Demand/Capability/Flow/Conditions/Thinking.
  • Constraint-first triage and outputs: Produces a clear diagnostic flow, an A3-lite problem statement, and actionable countermeasures including crisis-mode guidance for multi-system failures.

Example use cases:

  • “Our forecast is unreliable”: find whether the constraint is governance definitions, enablement/data spine issues, or broken execution cadence.
  • “Pipeline is weak / deals slip late”: isolate whether pipeline management, stage exit criteria, or qualification/flow is the actual bottleneck.
  • “We keep missing plan”: run the constraint logic to avoid piling on initiatives that don’t unlock revenue throughput.

Quick Start

Use the revops-diagnostic Skill to diagnose why your revenue system isn’t performing by prompting it with your top 3 symptoms, recent trend metrics (pipeline coverage, forecast variance, churn/NRR if relevant), and the segment/motion (inbound, outbound, renewals/expansion, or partner) you’re focused on.

Frequently Asked Questions about revops-diagnostic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of weak B2B pipeline and forecast variance?

Diagnosing revenue constraints requires identifying failures across governance, enablement, and ICP value loops. You run an IFA and Six Stages of Check workflow to pinpoint the weakest link in Information, Focus, or Action, then produce an A3-lite countermeasure plan.

What is the best way to diagnose why deals keep slipping late in the pipeline?

The best way to diagnose late deal slippage is applying constraint-first triage to isolate whether pipeline management, stage exit criteria, or qualification flow is the bottleneck. This avoids piling on initiatives that fail to unlock revenue throughput.

How do I troubleshoot cross-functional trust breakdowns and churn drops in RevOps?

Troubleshooting cross-functional trust breakdowns and churn drops requires running a system-layer diagnostic to locate the true constraint. You analyze Purpose, Demand, Capability, Flow, Conditions, and Thinking to generate targeted A3-lite countermeasures.

Can I use this diagnostic approach for multi-system revenue failures and crisis triage?

Yes, this diagnostic approach supports crisis triage for multi-system revenue failures. It applies constraint-based root cause analysis to identify complex failure patterns across B2B systems and generates prioritized crisis-mode countermeasures.

What information do I need to start a B2B revenue diagnostic?

Starting a B2B revenue diagnostic requires your top 3 symptoms, recent trend metrics including pipeline coverage and forecast variance, and your target segment or motion such as inbound, outbound, renewals, or partner channels.