PranavNagrecha/AwesomeSalesforceSkills / skills/admin/collaborative-forecasts
collaborative-forecasts
VerifiedSet up, configure or troubleshoot Salesforce Collaborative Forecasts: forecast types, forecast categories, rollup methods, quota management, forecast hierarchy, manager adjustments, pipeline inspection integration. Trigger keywords: forecast type, forecast category, cumulative rollup, individual rollup, quota, forecast adjustment, forecast hierarchy, opportunity splits forecasting, pipeline forecast. NOT for configuring the opportunity stages, sales processes or split types themselves — use admin/opportunity-management. NOT for territory-based forecasting setup — use admin/enterprise-territory-management. NOT for Classic/Customizable Forecasting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 36.4 KB |
| references/examples.md | markdown | 6.5 KB |
| references/gotchas.md | markdown | 22.4 KB |
| references/llm-anti-patterns.md | markdown | 8.5 KB |
| references/metadata-examples.md | markdown | 28.1 KB |
| references/well-architected.md | markdown | 12.8 KB |
| scripts/check_collaborative_forecasts.py | script | 38.8 KB |
| templates/collaborative-forecasts-template.md | markdown | 3.6 KB |
templates/collaborative-forecasts-template.md
View on GitHub# Collaborative Forecasts — Work Template
Use this template when configuring, auditing, or troubleshooting Collaborative Forecasts in a Salesforce org.
## Scope
**Skill:** `collaborative-forecasts`
**Request summary:** (fill in what the user asked for)
## Context Gathered
Record the answers to the Before Starting questions from SKILL.md here.
- **Org edition:** (Enterprise / Performance / Unlimited)
- **Collaborative Forecasts enabled?** (yes / no / unknown — check Setup > Forecasts Settings)
- **Number of existing active Forecast Types:** (0–4+)
- **Sales motions in scope:** (direct revenue / overlay splits / product family / territory / other)
- **Hierarchy type in use:** (role hierarchy / territory hierarchy / both)
- **Quotas required?** (yes / no — affects ForecastingQuota load step)
- **Rollup method preference:** (cumulative / single-category / not yet decided)
- **Known constraints:** (e.g., existing adjustments that must be preserved, specific fiscal year calendar)
## Forecast Types to Configure
For each Forecast Type needed, document:
| Forecast Type Name | Source Object | Measurement Field | Hierarchy | Period Type | Rollup Method |
|---|---|---|---|---|---|
| (e.g. AE Direct Revenue) | Opportunity | Amount | Role | Monthly | Cumulative |
| (e.g. SE Overlay) | Opportunity Splits | Amount | Role | Monthly | Cumulative |
## Stage-to-Category Mapping Review
List all active opportunity stages and their intended category:
| Stage Name | Forecast Category | Intentional? |
|---|---|---|
| Prospecting | Pipeline | Yes |
| Qualification | Pipeline | Yes |
| (add all stages) | | |
| Closed Won | Closed | Yes |
| Closed Lost | Omitted | Yes |
Flag any stages that look revenue-generating but are mapped to Omitted.
## Forecast User Enablement
List users who must appear in the forecast hierarchy:
| User Name | Role | ForecastEnabled | Action Needed |
|---|---|---|---|
| (name) | (role) | true / false | Set ForecastEnabled = true if false |
## Quota Load Plan (if applicable)
- **Forecast Type(s) requiring quotas:**
- **Period type (monthly / quarterly):**
- **Period start dates to load:**
- **Load method:** Data Loader / Import Wizard / API
- **ForecastingTypeId to use:** (query `SELECT Id, Name FROM ForecastingType` to retrieve)
## Approach
Which mode from SKILL.md applies?
- [ ] Mode 1 — Configure from scratch
- [ ] Mode 2 — Audit existing configuration
- [ ] Mode 3 — Troubleshoot data issues
Which patterns are in use and why:
## Checklist
Copy the review checklist from SKILL.md and tick items as you complete them.
- [ ] Collaborative Forecasts is enabled in Setup > Forecasts Settings
- [ ] All active opportunity stages are mapped to a forecast category (no unmapped stages)
- [ ] Omitted stage mapping is intentional
- [ ] Rollup method is documented and matches stakeholder requirements
- [ ] All active Forecast Types are within the 4-type default limit
- [ ] All expected forecast users have ForecastEnabled = true
- [ ] Each forecast user has the correct role or territory membership
- [ ] Quotas are loaded for the current period (if attainment display is required)
- [ ] Split-based types have Opportunity Splits enabled and splits populated
- [ ] Forecast adjustments are intentionally configured per stakeholder preference
- [ ] Manager adjustment availability communicated to managers (not available for split-based types)
## Notes
Record any deviations from the standard pattern and why.
- Rollup method change risk communicated to: (name / date)
- Adjustment export completed before any rollup method change: (yes / N/A)
- Quota period boundary dates validated against ForecastingPeriod object: (yes / N/A)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |