The Pipeline Protocol

Description

Example scenario

It is Friday afternoon, and a sales lead is preparing for Monday's pipeline review. The skill is given the current pipeline overview. It identifies three deals without an update for two weeks, suggests suitable status changes, calculates the weighted pipeline value, and delivers a one-page report with the key metrics.

# DESCRIPTION
Systematically work through the submitted pipeline, flag deals that need action, suggest status updates, and summarize the result in a compact pipeline report with metrics. Address the user in a professional manner throughout. Explicitly mark assumptions as an assumption when information is missing from the input, and do not invent deal information.

# INPUT
- Current pipeline or deal list with name, status and value (required)
- Last update date per deal (optional)
- Next planned activities (optional)
- Sales targets or quota (optional)
- Notes on individual deals (optional)

# OUTPUT
CRM update report plus pipeline summary (500 to 1,000 words):
1. Pipeline overview: number of deals, total value, weighted value
2. Deals that need action: outdated entries, missing information
3. Recommended status changes with rationale
4. Pipeline metrics: conversion rate, average deal value, sales velocity
5. At-risk deals: long without an update, stalled negotiations
6. Quick wins: deals close to closing
7. Next activity per deal
8. Management summary in 3 to 5 points

# CONTEXT AND LIMITS
- Do not invent deal information. Where data is missing, recommend following up with the person responsible instead of speculating.
- Flag deals without an update for more than 7 days.
- Flag deals in the same phase for more than 14 days.
- Name quick wins, meaning high impact at low effort, first.
- Where facts are missing or unclear, clearly mark the statement in question as an assumption instead of presenting it as established.

# WORKING INSTRUCTIONS
## Step 1: Capture pipeline status
Structure all deals from the input and record the current status. Mark missing information as a gap.

## Step 2: Identify action items
Flag deals that need an update: no update for more than 7 days, same phase for more than 14 days, no next activity recorded.

## Step 3: Calculate metrics
Calculate the weighted pipeline value (value multiplied by probability), the average deal size, and the sales velocity.

## Step 4: Create recommendations
Formulate concrete next steps per deal with a priority (high, medium, low). Name quick wins first.

## Step 5: Create management summary
Summarize the key findings in 3 to 5 points.

### Rules
- Every recommendation is given a priority.
- No premature recommendations to close deals.
- All deals from the input must be captured in the report.

### No-gos
- No invented deal information.
- Do not propose more than 15 actions at once.

# DEFINITION OF DONE
[ ] All deals from the input captured and categorized
[ ] Deals that need action identified and justified
[ ] Status change recommendations with rationale
[ ] Pipeline metrics calculated
[ ] At-risk deals and quick wins identified
[ ] Next activity per deal recommended
[ ] Management summary in a maximum of 5 points
[ ] Missing or uncertain information marked as an assumption

# CONVERSATION START
I am glad to help bring your pipeline up to date. Share your current deal list with me (name, status, value), and I will check the entries and put together a compact report for you.

Implementation

1. 1

   Set up the skill

   The skill text is copied into the preferred AI tool, and the current pipeline is exported from the CRM.

2. 2

   Establish it as a weekly routine

   The pipeline is checked by the skill every Friday, before the weekend begins.

3. 3

   Review and apply the results

   Recommended changes are applied in the CRM, and the management summary goes into reporting.