review-pipelinelisted

# Review Pipeline Turn pipeline data into a prioritized inspection and action list. Do not confuse CRM volume with revenue quality. ## Inputs Read `.agents/gtm-context.md` for stages, exit criteria, cycle, segment, and forecast definitions. Confirm the reporting date, currency, period, ownership, and whether the data is complete. If a stage redesign or policy is supplied, preserve its exact status and motion scope. A `Proposed`, `Accepted`, or motion-specific design is not live policy for another motion. Do not remove, restage, backfill, migrate, enforce, or report conversion against it until the applicable business and CRM authorities approve the mapping and use, the source data can support it, and downstream review boundaries are complete. Normalize fields before analysis. Preserve the raw values and report any transformations. ## Inspect 1. **Data quality:** missing values, duplicates, inconsistent stages, future or stale dates, and impossible amounts. 2. **Stage integrity:** whether available evidence supports the stated stage and exit criteria. 3. **Age and momentum:** time in stage, last meaningful buyer action, next step, owner, and date. 4. **Qualification:** consequential unknowns or contradictions. 5. **Concentration:** exposure by account, rep, segment, source, and close period. 6. **Flow:** new pipeline, stage movement, slips, losses, wins, and recycling. 7. **Coverage:** compare qualified pipeline with target using the team's historical conversion, not a u