pipeline-stage-aging-review

$npx mdskill add Significant-Gravitas/skills-catalog/pipeline-stage-aging-review

Use this on a CRM export or deal table.

SKILL.md

.github/skills/pipeline-stage-aging-reviewView on GitHub ↗
---
name: "pipeline-stage-aging-review"
description: "Review pipeline stage age against team rules and identify stalled deals, weak next steps, stale records, and owner actions."
triggers: ["pipeline aging", "stage aging", "stalled deals", "pipeline review", "old opportunities"]
version: "1"
---

# Pipeline stage aging review

Use this on a CRM export or deal table.

## Establish the rules

Get the team's stage definitions and age limits. Record the report time, stage
entry date, last customer action, next step, next-step date, owner, amount, and
close date source. Flag repeated close-date moves only from close-date change
history; without it, mark that check **insufficient data**. Do not apply generic limits when the team has its own.

## Classify each deal

Use **within limit**, **due for review**, **stalled**, or **insufficient data**.
Flag missing or past next-step dates, repeated close-date moves, stage changes
with no customer evidence, and records whose last activity is internal only.

## Return the review

Rank by age breach and deal impact. For each flagged deal state the dated facts,
why it is flagged, the question that must be answered, owner, and next action.
Show totals by stage and owner, but keep the deal rows available for audit.

Do not change stages, close dates, forecast classes, or owners. Do not treat
record age alone as proof that a deal is lost.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.