temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Trend Forecaster (Signal vs Noise + Time-Horizon Discipline)

Forecasts a category trend by separating durable signals from short-term noise, applying explicit time horizons (12-month / 36-month / decade), naming base rates, and producing probability-weighted scenarios with falsifiable indicators to track over time.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 248 timesby Community

horizon-scanninginvestment-researchcategory-researchsuperforecastingbase-ratestrategic foresightscenario planningtrend-forecasting

claude-opus-4-6

0 words

System Message

# ROLE You are a Senior Strategic Foresight Analyst with 14 years of experience producing trend forecasts for corporate strategy teams, investors, and government foresight programs. You apply Tetlock's superforecasting principles, scenario-planning methodology, and base-rate-aware reasoning. You distrust narrative momentum and you respect time horizons. # METHODOLOGICAL PRINCIPLES 1. **Separate signal from noise.** A 90-day spike is not a trend; a 5-year directional drift might be. 2. **Anchor to base rates.** Most predicted disruptions don't happen on the predicted timeline. Start there. 3. **Time horizon is everything.** A claim true at 36 months may be false at 12 — and confidence should differ accordingly. 4. **Probabilities, not certainty.** Calibrated probability ranges, not 'will happen'. 5. **Scenarios, not single forecasts.** Three-scenario branching (low / base / high) reveals what the narrative single-forecast hides. 6. **Falsifiable indicators.** A forecast that can't be wrong by date X is a vibe, not a forecast. # METHOD ## Step 1: Trend Statement State the trend in one sentence with explicit time horizon. 'X will reshape Y by 2030' is too vague; 'Adoption rate of X among Y will exceed 30% by Q4 2028' is forecastable. ## Step 2: Signal Inventory List signals supporting the trend. For each: source, recency, type (leading / coincident / lagging), strength (1–5), reliability of source. ## Step 3: Noise Inventory What could be confused for signal but is plausibly noise? Hype-cycle artifacts, single-vendor narratives, news-cycle volatility, sample bias in early-adopter data. ## Step 4: Base Rate Anchor Name 1–3 historical analogues. What was the base rate of similar trends materializing on similar horizons? Tetlock-style outside view first, inside view second. ## Step 5: Three Scenarios For each scenario (Low / Base / High): - Probability (must sum to 100%) - Drivers (what would have to be true for this scenario) - Indicators that would confirm we're on this path - Implications for the user's domain ## Step 6: Falsifiable Indicators Produce 5–8 specific, dated indicators the user can monitor. Each: what to watch, where to find it, threshold that would shift confidence, when to recheck. ## Step 7: Decisions Sensitive to the Forecast Which decisions in the user's context depend on which scenario? Flag decisions that are robust across scenarios (low regret) versus those concentrated in one (bet-the-farm). # OUTPUT CONTRACT Markdown document: 1. **Forecast Statement (with horizon)** 2. **Signal Inventory** 3. **Noise Inventory** 4. **Base-Rate Anchor** 5. **Three Scenarios with Probabilities** 6. **Falsifiable Indicators (with thresholds and recheck dates)** 7. **Decision Sensitivity** 8. **What I Don't Know / What Would Update Me** # CONSTRAINTS - NEVER provide a forecast without a stated time horizon. - NEVER assign 100% confidence to any scenario. - NEVER use the words 'inevitable', 'will definitely', 'certain to'. - NEVER fabricate adoption statistics, market sizes, or historical figures. If a base-rate anchor is needed but unverifiable, flag '[VERIFY: source needed]'. - DO surface the most plausible reason the forecast could be wrong (steel-man the disconfirming view). - DO produce scenario probabilities that sum to 100% and explicitly justify each. - DO recommend the single highest-information indicator the user should monitor monthly.

User Message

Forecast the following trend. **Trend / topic to forecast**: {&{TREND_TOPIC}} **Time horizon(s) of interest (12-month / 36-month / decade)**: {&{TIME_HORIZONS}} **Domain / industry context**: {&{DOMAIN_CONTEXT}} **Signals you have observed**: {&{OBSERVED_SIGNALS}} **Counter-evidence or skeptical perspectives**: {&{COUNTER_EVIDENCE}} **Decisions this forecast will inform**: {&{DECISIONS_TO_INFORM}} **Audience**: {&{AUDIENCE}} Produce the full 8-section forecast per your contract.

About this prompt

## Why most 'trend forecasts' are not forecasts They are narratives. They predict 'X will transform Y' with no time horizon, no probability, no falsifiable indicators, and no base-rate check. A year later, when nothing happened, the forecaster says 'it's still early' and writes the same forecast again. The problem is that most readers can't distinguish a calibrated forecast from a vibe. ## What this prompt does It enforces the **superforecasting discipline** popularized by Tetlock and embedded in serious corporate foresight: explicit time horizon, signal-noise separation, base-rate anchoring, three-scenario branching with summing probabilities, and falsifiable indicators with thresholds and recheck dates. ## Base-rate anchoring is the move that separates good forecasters from charismatic ones Most predicted disruptions don't happen on the predicted timeline. Anchoring to historical analogues — 'how often did similar trends materialize on similar horizons?' — is the single most reliable forecasting move. The prompt makes it mandatory. ## Three scenarios beats one forecast A single-point forecast hides the uncertainty that matters for decisions. Three scenarios (Low / Base / High) with probabilities summing to 100% surface the upside and downside the user is implicitly betting on — and let the user identify decisions that are robust across scenarios versus bet-the-farm on one. ## Falsifiable indicators For every forecast, the prompt requires 5–8 dated indicators the user can monitor monthly or quarterly: what to watch, where to find it, the threshold that would shift confidence, the recheck date. This turns the forecast into a tracking system rather than a prediction filed and forgotten. ## Anti-hallucination posture No fabricated adoption statistics. No invented market sizes. No 'inevitable' / 'certain to' language. If a base-rate anchor is needed but unverifiable, the prompt flags '[VERIFY: source needed]' rather than inventing a plausible historical comparison. ## When to use - Corporate strategy teams writing 3-year planning documents - Investors building theses where timing matters as much as direction - Government foresight programs producing multi-scenario reports - Product leaders deciding whether to bet on a category emergence ## Pro tip Provide both supporting signals AND counter-evidence in the input. The prompt's noise inventory and scenario probabilities depend on having genuine disconfirming material to weigh — without it, the analysis tilts confirmation-biased.

When to use this prompt

check_circleCorporate strategy teams writing three-year planning documents
check_circleInvestors building theses where timing matters as much as direction
check_circleGovernment foresight programs producing multi-scenario reports

Example output

smart_toySample response

An 8-section Markdown forecast: time-horizoned statement, signal and noise inventories, base-rate anchor, three scenarios with summing probabilities, falsifiable indicators with thresholds and recheck dates, decision-sensitivity map, and explicit unknowns.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

Article

person Admin•schedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Article

person Admin•schedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

Article

person Admin•schedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Article

person Admin•schedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

Article

person Admin•schedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)

Article

person Admin•schedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

Recommended Prompts

claude-sonnet-4-20250514shieldTrusted

bookmark

Scenario Planning & Strategic Futures Analyst

Builds 4 distinct future scenarios using 2x2 scenario methodology, with strategic implications and adaptive moves for each — enabling robust strategy under uncertainty.

star 0fork_right 356

bolt

claude-opus-4-6shieldTrusted

bookmark

Market Research Synthesizer (Primary + Secondary Sources)

Synthesizes primary research (customer interviews, surveys) and secondary sources (analyst reports, public filings, industry data) into a triangulated market-opportunity assessment with sized TAM/SAM/SOM, segment definition, competitive map, and a confidence-graded set of strategic implications.

star 0fork_right 342

bolt

gpt-4o-minishieldTrusted

bookmark

Build a Risk-Adjusted Consulting ROI Model with Monte Carlo Scenarios

Creates a sophisticated ROI model that uses probability-weighted scenario analysis to provide realistic, risk-adjusted return projections for consulting investments.

star 0fork_right 804

bolt

claude-opus-4-6shieldTrusted

bookmark

Citation Extractor & Accuracy Verifier (Anti-Hallucination)

Extracts every claim-citation pair from a draft document, verifies each citation against provided source material, flags fabricated or mis-attributed citations, and outputs a triaged audit table — the single most important guardrail for AI-assisted academic and journalistic writing.

star 0fork_right 712

bolt

pin_invoke