Pipeline data quality | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Missing-field, stale-date and stage-consistency audit.

Start with: Pipeline export and field/stage definitions.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Establish the required fields, stage definitions, valid dates and expected ownership rules.
Inspect the supplied pipeline for missing fields, duplicate opportunities, stale dates and inconsistent stages.
Separate an obvious correction from a change needing the record owner's judgment. Preserve original identifiers and values in the review.
Return an exception list and proposed corrections. Do not silently rewrite source data or treat guessed close dates as verified.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: pipeline-data-quality
description: "Prepare missing-field, stale-date and stage-consistency audit. Use for this workflow with supplied business information."
---

# Pipeline data quality

## Inputs and purpose

Use this workflow to prepare: Missing-field, stale-date and stage-consistency audit.

Start with: Pipeline export and field/stage definitions.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Establish the required fields, stage definitions, valid dates and expected ownership rules.

2. Inspect the supplied pipeline for missing fields, duplicate opportunities, stale dates and inconsistent stages.

3. Separate an obvious correction from a change needing the record owner's judgment. Preserve original identifiers and values in the review.

4. Return an exception list and proposed corrections. Do not silently rewrite source data or treat guessed close dates as verified.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).