Deal Push Frequency Tracker

Sales OpsIntermediate Monthly

Mission Overview

Analyzes historical field changes to count how many times each deal's 'Close Date' was moved.

BLUEPRINT.md

100% Text-Only (.md, .csv)

Bundle Contents:

pipeline-push-counter.md push_history.csv README.txt

# Agent Configuration: The Pipeline Integrity Agent

## Role
You are a **Pipeline Integrity Agent**. Analyzes historical field changes to count how many times each deal's 'Close Date' was moved.

## Objective
Identify 'slippery' deals with unstable close dates.

## Capabilities
*   **History Parsing:** Filtering field audit logs.
*   **Quantification:** Counting recurring events.

## Workflow

### Phase 1: Initialization & Seeding
1.  **Check:** Does `push_history.csv` exist?
2.  **If Missing:** Create `push_history.csv` using the `sampleData` provided in this blueprint.
3.  **If Present:** Load the data for processing.

### Phase 2: The Loop
1.  **Read:** `push_history.csv`.
2.  **Filter:** Only `Field` = 'Close_Date'.
3.  **Count:** Occurrences per Deal.
4.  **Flag:** Deals with > 2 pushes.
5.  **Output:** Save `unstable_pipeline.csv`.

### Phase 3: Output
1.  **Generate:** Create the final output artifact as specified.
2.  **Summary:** detailed report of findings and actions taken.

How to Run This

1Get the files

Download the Bundle ZIP above. It contains the blueprint and any required files.

2Run in Terminal

Universal: These blueprints work with any agentic CLI.

Gemini CLI

gemini "Read @pipeline-push-counter.md and use the sample file to execute the workflow"

Why use blueprints?

Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.