← ClaudeAtlas

forecast-saleslisted

Create, inspect, or explain a B2B sales forecast using CRM opportunities, historical conversion, pipeline changes, seller calls, or scenario assumptions. Use for commit and best-case calls, monthly or quarterly forecasting, forecast risk, rollups, coverage, sensitivity analysis, or explaining a forecast to leadership.
zarif3624/gtm-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill zarif3624/gtm-skills
# Forecast Sales Produce an auditable estimate with explicit assumptions, uncertainty, and downside. A forecast is a decision tool, not a target restated as confidence. ## Inputs Read `.agents/gtm-context.md`. Confirm: - as-of date, forecast period, currency, and target; - opportunity scope and ownership; - stage and forecast-category definitions; - historical win, slip, and cycle data available; - treatment of renewals, expansions, usage revenue, and one-time revenue. ## Data Checks Check duplicates, missing amounts, close dates outside the period, stale opportunities, inconsistent currencies, unsupported stages, and required milestones after the close date. Report exclusions and transformations. ## Partial Or Aggregate Data When deal-level rows or calibrated rates are missing, do not invent an allocation or stop at a refusal. **Minimum response contract:** Even when the user asks for one exact number, produce a compact forecast artifact rather than only a warning or formula. It must include: - closed revenue, central estimate, supportable forecast range or `Unknown`, theoretical ceiling, and gap to target; - downside, expected, and upside scenarios, using `Unknown` where a value is not supportable; - included, excluded, and unallocatable contributions plus concentration or timing limits; - the minimum additional evidence needed; and - the governance checkpoint from the output template. - Calculate exact supported values such as closed revenue. - Show the requeste