forecast-discipline — Claude Code skill for forecast methodology
forecast-discipline — a Claude Code skill that builds forecast-call methodology: commit/best case/pipeline tiers, inspection checklists, and accuracy thresholds. Runs when you prepare weekly or monthly sales forecasts.
Apache-2.0 ★ 450 updated 2026-04-03
npx skills add gtmagents/gtm-agents --skill forecast-discipline -a claude-codeWhat forecast-discipline does
Structures forecast calls by defining tiers (commit, best case, pipeline, upside) with exit criteria, inspection rubrics, and review cadences. Includes templates: forecast call agenda with checklist, commit change request form, KPI guardrail sheet (pipeline coverage ≥4x for new logo, ≥3x for expansion, commit accuracy ≥90%, slip rate ≤10%), inspection worksheet with standard questions (deal health, decision process, risk plan), and escalation memo for the Chief Strategy Officer when guardrails are breached.
Requires written rationale for commit changes >5% week-over-week, syncs inspections with CRM hygiene dashboards, and triggers a RevOps remediation sprint if a guardrail is breached twice in a quarter. Cadence: weekly manager inspections, bi-weekly cross-functional sync with Marketing Director and Customer Success Manager, monthly accuracy retro and rubric adjustment. CSO briefing triggers when coverage drops below 3.5x or commit accuracy falls under 85%.
What it helps with
- build unified forecast-call methodology with commit and best case tiers
- set pipeline coverage and forecast accuracy thresholds with alerts
- standardize deal inspection questions using MEDDIC/BANT prompts
- prepare CSO escalation when KPI guardrails are breached
- run forecast accuracy retro and adjust inspection rubric
Example prompts for the agent
- Draft the weekly forecast call agenda with commit deal inspection checklist
- Check pipeline coverage against GTM Agents thresholds and generate CSO escalation memo
- Build KPI guardrail sheet: coverage, slip rate, commit accuracy with alert values
How to install forecast-discipline
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill forecast-discipline -a claude-code2Manually: put the files in place
~/.claude/skills/forecast-discipline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/forecast-discipline/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill forecast-discipline -a codex2Manually: put the files in place
.agents/skills/forecast-discipline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill forecast-discipline -a cursor2Manually: put the files in place
.cursor/skills/forecast-discipline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gtmagents/gtm-agents plugins/sales-pipeline/skills/forecast-discipline2Manually: put the files in place
.github/skills/forecast-discipline/SKILL.md1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill forecast-discipline -a gemini-cli2Platform CLI
gemini skills install https://github.com/gtmagents/gtm-agents --path plugins/sales-pipeline/skills/forecast-disciplineManually: put the files in place
.devin/skills/forecast-discipline/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about forecast-discipline
How to install forecast-discipline in Claude Code?
Run npx skills add gtmagents/gtm-agents --skill forecast-discipline -a claude-code. The skill will be available at ~/.claude/skills/forecast-discipline/SKILL.md.
What does forecast-discipline do?
Builds forecast-call methodology: defines forecast tiers (commit, best case, pipeline), inspection checklists, accuracy thresholds (commit accuracy ≥90%, slip rate ≤10%), and review cadences. Includes agenda templates, commit change request form, and CSO escalation memo.
What KPI guardrails does the skill use?
Pipeline coverage ≥4x for new logo and ≥3x for expansion, commit accuracy ≥90% (warning at 85%), slip rate ≤10% (immediate review if >15%), and 95% of commit deals must have logged next steps and a mutual action plan.
Source text
SKILL.md · Apache-2.0
--- name: forecast-discipline description: Use to drive consistent forecast methodology, grading, and inspection cadences. --- # Forecast Discipline Guide Skill ## When to Use - Running weekly/monthly forecast calls. - Coaching managers on commit/best case criteria. - Aligning go-to-market teams on inspection processes. ## Framework 1. **Forecast Tiers** – define commit, best case, pipeline, upside with clear exit criteria. 2. **Grading Rubric** – outline inspection questions and data required for each tier. 3. **Cadence** – schedule prep steps, live inspections, and follow-up check-ins. 4. **Accountability** – log actions, approvals, and exceptions tied to each commit change. 5. **Continuous Improvement** – review accuracy vs actuals, adjust rubric/cadence quarterly. ## Templates - Forecast call agenda + checklist. - Commit change request form. - Accuracy retro template with action items. - **GTM Agents Inspection Worksheet** – standardized questions (deal health, decision process, paper process, risk plan) @puerto/README.md#244-271. - **KPI Guardrail Sheet** – pipeline coverage, conversion %, slip rate with alert thresholds. - **Escalation Memo Template** – summary for Chief Strategy Officer when forecast misses guardrails. ## Tips - Keep commit changes transparent and documented. - Incorporate MEDDIC/BANT prompts into inspection scripts. - Pair with CRM hygiene dashboards to ensure data supports forecast claims. - Mirror GTM Agents cadence: Monday management prep, Tuesday deal desk sync, Thursday exec forecast call. - Require written rationale for any commit movement >5% week over week. - If guardrail breached twice in a quarter, trigger RevOps remediation sprint (see lifecycle rip-cord procedures). ## GTM Agents Forecast Governance Overlay 1. **Call Structure** - Start with KPI guardrail review (coverage, wins, slip rate) vs GTM Agents thresholds. - Run tiered inspection (commit → best case → upside) with standard worksheet. - Assign owners for each risk + resolution plan. 2. **Cadence & Artifacts** - Weekly: manager inspections + Sales Director roll-up. - Bi-weekly: cross-functional sync with Marketing Director + Customer Success Manager for pipeline risks. - Monthly: accuracy retro + adjustments to rubric. 3. **Escalation** - Trigger CSO briefing when coverage <3.5x or commit accuracy slips below 85%. - Provide summary memo using Escalation Template. ## KPI Guardrails (GTM Agents Reference) - Pipeline coverage ≥4x for new logo, ≥3x for expansion. - Commit accuracy ≥90% in-quarter; warn at 85%. - Slip rate ≤10% QoQ; immediate review if >15%. - Stage hygiene: 95% of commit deals must have next steps + mutual action plan logged. ## Inspection Questions (Excerpt) 1. What changed since last call? (Deal, champion, procurement, competition) 2. Do we have verifiable next steps and dates? Who owns them? 3. What negative signals exist? (product gaps, budget freeze, legal hurdles) 4. How will this impact coverage if it slips—what backfill exists? Use these prompts in every inspection to match GTM Agents Sales Director rigor. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents