pipeline-health

<!-- Generated from `.claude/skills/_available/sales/pipeline-health/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> ## Purpose Produce a dated, evidence-backed view of pipeline coverage, velocity, conversion, concentration, and forecast confidence. The skill calculates what the supplied data supports and leaves policy judgments unknown when the team's definitions are absent. ## Usage - `/pipeline-health` — review the current confirmed reporting period - `/pipeline-health [period]` — review a named month, quarter, or date range - `/pipeline-health forecast` — focus on explicit forecast categories and gaps ## Evidence, authority, and recovery Set a report `as-of` timestamp before reading data. Attach field provenance to every target, deal value, stage, probability, forecast category, date, benchmark, and calculated claim: source path or record ID, source event date, and read as-of time. A file modified time is only a discovery clue, never a substitute for a business event date. - Use only configured and confirmed stages, targets, probabilities, forecast categories, thresholds, and benchmarks for the requested period. Record the applicable configuration source and effective date. If one is absent, stale, contradictory, or unconfirmed, mark it `Unknown`; never invent a replacement or import a generic sales convention. - Missing differs from zero. A blank, unreadable, absent, or conflicting value is `Unknown`; zero is valid only when the author...