forecast
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
Best use case
forecast is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
Teams using forecast should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/forecast/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How forecast Compares
| Feature / Agent | forecast | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# /forecast > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate a weighted sales forecast with risk analysis and commit recommendations. ## Usage ``` /forecast [period] ``` Generate a forecast for: $ARGUMENTS If a file is referenced: @$1 --- ## How It Works ``` ┌─────────────────────────────────────────────────────────────────┐ │ FORECAST │ ├─────────────────────────────────────────────────────────────────┤ │ STANDALONE (always works) │ │ ✓ Upload CSV export from your CRM │ │ ✓ Or paste/describe your pipeline deals │ │ ✓ Set your quota and timeline │ │ ✓ Get weighted forecast with stage probabilities │ │ ✓ Risk-adjusted projections (best/likely/worst case) │ │ ✓ Commit vs. upside breakdown │ │ ✓ Gap analysis and recommendations │ ├─────────────────────────────────────────────────────────────────┤ │ SUPERCHARGED (when you connect your tools) │ │ + CRM: Pull pipeline automatically, real-time data │ │ + Historical win rates by stage, segment, deal size │ │ + Activity signals for risk scoring │ │ + Automatic refresh and tracking over time │ └─────────────────────────────────────────────────────────────────┘ ``` --- ## What I Need From You ### Step 1: Your Pipeline Data **Option A: Upload a CSV** Export your pipeline from your CRM (e.g. Salesforce, HubSpot). I need at minimum: - Deal/Opportunity name - Amount - Stage - Close date Helpful if you have: - Owner (if team forecast) - Last activity date - Created date - Account name **Option B: Paste your deals** ``` Acme Corp - $50K - Negotiation - closes Jan 31 TechStart - $25K - Demo scheduled - closes Feb 15 BigCo - $100K - Discovery - closes Mar 30 ``` **Option C: Describe your territory** "I have 8 deals in pipeline totaling $400K. Two are in negotiation ($120K), three in evaluation ($180K), three in discovery ($100K)." ### Step 2: Your Targets - **Quota**: What's your number? (e.g., "$500K this quarter") - **Timeline**: When does the period end? (e.g., "Q1 ends March 31") - **Already closed**: How much have you already booked this period? --- ## Output ```markdown # Sales Forecast: [Period] **Generated:** [Date] **Data Source:** [CSV upload / Manual input / CRM] --- ## Summary | Metric | Value | |--------|-------| | **Quota** | $[X] | | **Closed to Date** | $[X] ([X]% of quota) | | **Open Pipeline** | $[X] | | **Weighted Forecast** | $[X] | | **Gap to Quota** | $[X] | | **Coverage Ratio** | [X]x | --- ## Forecast Scenarios | Scenario | Amount | % of Quota | Assumptions | |----------|--------|------------|-------------| | **Best Case** | $[X] | [X]% | All deals close as expected | | **Likely Case** | $[X] | [X]% | Stage-weighted probabilities | | **Worst Case** | $[X] | [X]% | Only commit deals close | --- ## Pipeline by Stage | Stage | # Deals | Total Value | Probability | Weighted Value | |-------|---------|-------------|-------------|----------------| | Negotiation | [X] | $[X] | 80% | $[X] | | Proposal | [X] | $[X] | 60% | $[X] | | Evaluation | [X] | $[X] | 40% | $[X] | | Discovery | [X] | $[X] | 20% | $[X] | | **Total** | [X] | $[X] | — | $[X] | --- ## Commit vs. Upside ### Commit (High Confidence) Deals you'd stake your forecast on: | Deal | Amount | Stage | Close Date | Why Commit | |------|--------|-------|------------|------------| | [Deal] | $[X] | [Stage] | [Date] | [Reason] | **Total Commit:** $[X] ### Upside (Lower Confidence) Deals that could close but have risk: | Deal | Amount | Stage | Close Date | Risk Factor | |------|--------|-------|------------|-------------| | [Deal] | $[X] | [Stage] | [Date] | [Risk] | **Total Upside:** $[X] --- ## Risk Flags | Deal | Amount | Risk | Recommendation | |------|--------|------|----------------| | [Deal] | $[X] | Close date passed | Update close date or move to lost | | [Deal] | $[X] | No activity in 14+ days | Re-engage or downgrade stage | | [Deal] | $[X] | Close date this week, still in discovery | Unlikely to close — push out | --- ## Gap Analysis **To hit quota, you need:** $[X] more **Options to close the gap:** 1. **Accelerate [Deal]** — Currently [stage], worth $[X]. If you can close by [date], you're at [X]% of quota. 2. **Revive [Stalled Deal]** — Last active [date]. Worth $[X]. Reach out to [contact]. 3. **New pipeline needed** — You need $[X] in new opportunities at [X]x coverage to be safe. --- ## Recommendations 1. [ ] [Specific action for highest-impact deal] 2. [ ] [Action for at-risk deal] 3. [ ] [Pipeline generation recommendation if gap exists] ``` --- ## Stage Probabilities (Default) If you don't provide custom probabilities, I'll use: | Stage | Default Probability | |-------|---------------------| | Closed Won | 100% | | Negotiation / Contract | 80% | | Proposal / Quote | 60% | | Evaluation / Demo | 40% | | Discovery / Qualification | 20% | | Prospecting / Lead | 10% | Tell me if your stages or probabilities are different. --- ## If CRM Connected - I'll pull your pipeline automatically - Use your actual historical win rates - Factor in activity recency for risk scoring - Track forecast changes over time - Compare to previous forecasts --- ## Tips 1. **Be honest about commit** — Only commit deals you'd bet on. Upside is for everything else. 2. **Update close dates** — Stale close dates kill forecast accuracy. Push out deals that won't close in time. 3. **Coverage matters** — 3x pipeline coverage is healthy. Below 2x is risky. 4. **Activity = signal** — Deals with no recent activity are at higher risk than stage suggests.
Related Skills
pipeline-review
Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
draft-outreach
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
daily-briefing
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
create-an-asset
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
competitive-intelligence
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
call-summary
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
synthesize-research
Synthesize user research from interviews, surveys, and feedback into structured insights. Use when you have a pile of interview notes, survey responses, or support tickets to make sense of, need to extract themes and rank findings by frequency and impact, or want to turn raw feedback into roadmap recommendations.
stakeholder-update
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.