---
name: pipeline-deal-health-analyzer
description: Analyze a sales pipeline to expose stalled deals, forecast risk, and the actions that move revenue. Use this skill whenever a user wants a pipeline review, deal health analysis, forecast scrub, or says 'review my pipeline', 'which deals are actually going to close', 'my forecast keeps slipping', or pastes a list of open deals. Trigger whenever open opportunities need triage into a defensible forecast and a prioritized action list.
---

# Pipeline and Deal Health Analyzer

## What this does and why it matters
Pipelines lie. Deals sit in a stage because no one moved them, close dates slip because they were wishful, and reps chase the loud deals over the winnable ones. This skill scrubs a set of open deals, flags the health risks, and returns a prioritized action list, converting a messy pipeline into a defensible forecast and a clear plan for the week.

## Inputs to gather
1. The open deals with as much as available: stage, amount, close date, age in stage, last activity, and any notes.
2. The sales stages and what each requires to advance.
3. Typical sales cycle length, if known.

## Method

### 1. Flag the health risks per deal
For each deal check: stalled (age in stage well beyond normal), no recent activity, a close date that keeps slipping, a single-threaded relationship, missing an engaged economic buyer, or no confirmed next step. Each flag is a specific risk, not a vibe.

### 2. Re-read the forecast honestly
Sort deals into Commit (evidence supports the close date), Best case (possible, needs work), and Unlikely (should be nurtured or dropped). Push back on close dates unsupported by a real decision process.

### 3. Find the highest-leverage actions
Identify the few moves that most improve the forecast: the deal that needs multi-threading, the stalled deal that needs a reframe or a walk-away, the strong deal that needs a close plan.

### 4. Surface pattern problems
If many deals stall at the same stage, that is a process problem worth naming.

## Output format
ALWAYS use:

# Pipeline Review | [Date]
## Forecast (Commit / Best case / Unlikely, with amounts)
## Deal-by-deal flags (deal | risks | recommended action)
## Highest-leverage actions this week (ranked)
## Pattern problems (systemic stalls)
## Deals to nurture or drop

## Anti-patterns to avoid
- Accepting rep-provided close dates without scrutiny.
- Treating deal size as the only priority (a huge unqualified deal is not a priority).
- Letting zombie deals inflate the pipeline forever.

## Example
A deal stuck 60 days in "proposal" with no activity and a single contact is flagged single-threaded and stalled, moved to Unlikely, with "get the champion to introduce the budget owner or disqualify" as the action.