Claude Skill

Pipeline Review Brief

Structures your top 5 deals + risks for a 1:1 with your manager.

Download skill (.zip)Or download whole pack

What it does

Before a pipeline review with your manager, this skill turns your raw deal notes into a structured brief: top deals by stage, status changes since last review, risks worth flagging, and the asks you need from your manager. Designed to make 1:1s productive instead of status theater.

When to use

✓Before weekly or biweekly pipeline review with your manager
✓You have ~5-10 deals in flight and want a clean snapshot

When not to use

✗Your manager wants raw CRM data — they'll pull it themselves
✗It's a tactical 1:1 about a specific deal, not pipeline-wide

Install

Download the .zip, then unzip into your Claude skills folder.

mkdir -p ~/.claude/skills
unzip ~/Downloads/pipeline-review-brief.zip -d ~/.claude/skills/

# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.

SKILL.md

---
name: pipeline-review-brief
description: Structures top 5 sales deals + risks into a clean brief for manager 1:1 pipeline reviews.
---

# Pipeline Review Brief

When the user provides raw deal notes before a pipeline review, structure them into a clean brief.

## Required input

Per deal:
- Company name
- Deal size (annual or total)
- Current stage
- Last touch (date + outcome)
- What's blocking, if anything

If the user dumps a wall of notes, ask which 5-7 deals matter most and focus on those. A pipeline review is not a roll-call.

## Output structure

### Top deals (table format)

| Company | Stage | Size | Confidence | Risk |
|---------|-------|------|-----------|------|

Confidence: high / medium / low — and one-line reason.
Risk: the specific thing that could kill this deal, if anything.

### What changed since last review (3 bullets max)

The actual movement — deals advanced, deals slipped, new opportunities. Skip "no change" deals.

### Where I need your help (2-3 specific asks)

What the user needs from the manager. Examples:
- "Need exec sponsor for Acme — their CFO wants assurance"
- "Pricing approval below our floor for Globex"
- "Coaching on objection: how do I respond to 'we built it ourselves'?"

If the user has no asks, push back: a pipeline review without asks is just status reporting.

### Deals worth disqualifying

Deals that look good in CRM but should probably be killed. Be honest. Manager appreciates this more than fake hope.

## Constraints

- Total brief fits on one printed page (~300 words)
- No "tracking nicely" / "going well" — those are filler
- Every claim should reference specific evidence (last meeting, customer quote, signal)
- If a deal is stuck, name the actual blocker — not "they're busy"

Example prompts

Once installed, try these prompts in Claude:

Build my pipeline brief for tomorrow. [paste raw deal notes for Acme, Globex, Initech, Hooli, Pied Piper]

Related prompts

Don't want to install a skill? These prompts in /prompts cover similar ground for one-shot use:

productivity prompts