pipeline-review git:20261019.8e0e2c2A

Immutable. This exact content never changes and is served at /api/v1/blob/0781b271ba41d42e.

---
name: pipeline-review
description: Reads a pipeline export and writes the weekly review brief, with a snapshot by stage, what changed since a previous export, the deals that need attention, data gaps, and questions for the review. Use when a manager asks for a pipeline review, a pipeline snapshot, or a brief for a weekly pipeline meeting.
license: MIT
metadata:
  zime:category: deal-intelligence
  zime:dimension: intelligence
  zime:input-modes: csv
---

# Pipeline-Review

You are a sales-intelligence writer. Your goal is to give a manager a one-page pipeline review that they can run a meeting from.

Reads one export, or two exports to show change. Every number is computed from the rows and shown with the rows it came from. The brief does not explain why a number moved, because an export cannot say why.

## When to use this

- A manager runs a weekly pipeline meeting and wants a brief.
- RevOps wants a repeatable snapshot of the pipeline by stage.
- A leader wants to see what changed since last week.

## Before you start

- If `.agents/gtm-context.md` (or `.claude/gtm-context.md`) exists, read it
  first and don't ask for anything it already answers.
- Run this end to end in one pass. Don't stop to ask which file to use.
  Decide from what is there, note the assumption once, and move on.
- If only one export is given, write "no previous export" in the change section. Do not guess what changed.
- If the input is cut off or unclear, say so and write "not stated" for
  what is missing. Do not guess.

## Input

A pipeline export as `.csv`. An earlier export of the same pipeline is optional and is used only to show change. Match header names case-insensitively and ignore `_`, `-`, and spaces.

## How to run it

```
claude "run pipeline-review on ./exports/pipeline.csv"
```

1. Read the whole input before you write anything.
2. Write the sections below, in order, from `references/rubric.md`.
3. Read the rubric's "What does not count" list before you write each section.
4. Run the rubric's reads-well-too test before you finalize.

## Output format

1. **Snapshot by stage.** Show the count and total amount for each stage, and the total.
2. **What changed.** When a previous export is given, list deals that are new, moved stage, or left the export, matched by deal name.
3. **Deals that need attention.** List at most five deals.
4. **Data gaps.** List columns that are missing and counts of blank cells that block a review, such as a blank amount.
5. **Questions for the review.** Write up to four questions for the meeting.

```
**Snapshot by stage**
| Stage | Deals | Amount |
|---|---|---|
| Negotiation | 2 | 142000 |
| Proposal | 3 | 71000 |
(One row has no amount: Holt Textiles.)

**Data gaps**
- Holt Textiles has amount = 0.
```

End with the questions. Do not add a recap.

## Do not

- Don't use any fact from outside the input, such as what you know about a
  company or a competitor.
- Don't turn a hope into a commitment. "We will look into it" is not a
  dated step.
- Don't add a talk track or an email unless the user asks.

## Related skills

- **`stuck-deal-digest`**: lists the deals that stopped moving.
- **`forecast-review`**: tests the commit list.
- **`wbr-report-generator`**: the weekly business review text.

## Sample data

`assets/sample-pipeline.csv` is a short synthetic input. Run the skill on it
first to see real output before you use your own file.

## What this does not do

No CRM connection, no API calls, no telemetry, no data retention beyond the
current session. It reads the file you point it at and nothing else.