pipeline-stage-definition-and-exit-criteria

Define auditable pipeline stages with entry and exit criteria.

11|1|Updated Mar 17, 2026

Search Tags:#crm #governance #pipeline #stages #forecasting #qualification #revops

Ready to run

npx skills add https://github.com/nthnclrk/enablement-skills --skill pipeline-stage-definition-and-exit-criteria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pipeline-stage-definition-and-exit-criteria
Source: https://github.com/nthnclrk/enablement-skills/tree/main/skills/pipeline-stage-definition-and-exit-criteria
Command: npx skills add https://github.com/nthnclrk/enablement-skills --skill pipeline-stage-definition-and-exit-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Defines auditable sales stages with entry and exit criteria and required proof to help managers inspect progression and RevOps enforce governance.

Core Features & Use Cases

Stage card templates with purpose, entry criteria, exit criteria, and required proof.
Anti-patterns and exception paths to guard stage transitions.
CRM mapping guidance and governance notes to align with forecasting and reporting.
Use cases include deal-inspection and forecast risk assessment across MEDDPICC or similar methods.

Quick Start

Create a new stage card for a deal in progress with defined entry, exit criteria, and proof requirements.

Frequently Asked Questions about pipeline-stage-definition-and-exit-criteria

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

FAQPage Schema

How do I define auditable pipeline stages with clear exit criteria in CRM?▼

Auditable pipeline stages require a stage card template defining purpose, entry criteria, exit criteria, required proof, owner, and anti-patterns. This enforces consistent deal progression and provides governance outputs like CRM mapping notes and transition plans for RevOps forecasting.

What is a stage card and how does it enforce sales deal progression?▼

A stage card is a template that defines deal progression rules using purpose, entry criteria, exit criteria, required proof, and anti-patterns. It enforces consistent sales deal progression by requiring evidence before transitions and mapping directly to CRM governance notes and reporting.

How do I map MEDDPICC qualification to CRM pipeline stages?▼

Mapping MEDDPICC to pipeline stages involves creating stage cards with entry and exit criteria tied to qualification evidence. Required proof fields ensure deals meet MEDDPICC standards before advancing, while CRM mapping notes align stage transitions with forecasting and reporting governance.

Can I use pipeline stage exit criteria for deal inspection and forecast risk assessment?▼

Pipeline stage exit criteria support deal inspection and forecast risk assessment by providing auditable proof requirements for each transition. Managers compare active deals against defined criteria and anti-patterns to identify stalled opportunities and enforce RevOps governance across new business and expansion motions.

What is the best way to prevent invalid stage transitions in sales pipelines?▼

Preventing invalid stage transitions requires defining anti-patterns and exception paths within stage cards. By specifying required proof and exit criteria, RevOps can block deals from advancing without evidence, ensuring CRM reporting and forecasting remain accurate and auditable.

How do pipeline stage definitions work for enterprise and expansion sales motions?▼

Pipeline stage definitions apply to enterprise and expansion sales by standardizing deal progression across motions. Stage cards enforce consistent entry and exit criteria, required proof, and owner accountability, while governance outputs align CRM mapping and transition plans for accurate forecasting.