Free Forecast Call Agenda Prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: forecast-call-agenda
description: "Run a forecast meeting that tests evidence, exposes risk, changes decisions, and assigns next actions instead of collecting updates."
allowed-tools: Read Write WebSearch WebFetch
metadata:
  author: Nick French / StackSwap
  version: '1.0'
  product: Operator Playbook
---

# Forecast Call Agenda

Forecast is a decision and inspection meeting, not a performance of confidence.

## When to use it

Use for weekly forecast, month-end, quarter-end, or a forecast reset. Do not use it to read CRM fields aloud or let unsupported optimism pass as judgment.

## Inputs to collect

Collect target, period, stage and exit rules, forecast categories, deal evidence, slips, pipeline health, conversion assumptions, rep/manager context, and decision rights.

## Method

1. Start with target, gap, evidence quality, and the few changes since last review.
2. Inspect exceptions: new commitments, pushed dates, weak next steps, single-threaded deals, and unsupported category changes.
3. Ask what must be true, what evidence exists, what is missing, and what action can change the outcome.
4. Separate commit, best case, pipeline, and upside with explicit inclusion rules.
5. End with owners, dates, escalation, forecast change log, and next inspection.

## Output

Produce a time-boxed agenda, pre-read, evidence questions, exception queue, forecast decision log, action register, escalation rules, and accuracy review.

## Verification and failure modes

Compare forecasts to later outcomes and code slip reasons. Guard against status theater, activity as evidence, recency bias, manager overrides without proof, and actions with no owner or date.

## Quality gate

Every forecasted deal or number must have an evidence basis, confidence, next test, and accountable owner.

Free forever. No email gate.