foresight

Generates dated, falsifiable predictions with accelerants, blockers, weak signals, and kill-signals.

4|1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/radarist/structured-analytic-skills --skill foresight-radarist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: foresight
Source: https://github.com/radarist/structured-analytic-skills/tree/main/skills/foresight
Command: npx skills add https://github.com/radarist/structured-analytic-skills --skill foresight-radarist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Vague forecasts like "X will happen soon" can never be checked or scored, so decisions about timing rest on unfalsifiable claims. This Skill turns a timing question into one dated, numeric-confidence prediction with the evidence, watchlist, and retraction conditions needed to track and later score it. ## Core Features & Use Cases - Dated falsifiable prediction: Produces a single milestone with an absolute date and a numeric confidence drawn from defined confidence bands (0.5–0.7 marked directional, below 0.5 withheld). - Accelerants and blockers with lead times: Lists three observable forces on each side, each with a lead time in months, so a wait-or-commit decision can be timed against early-warning windows. - Weak signals and kill-signals: Commits to three weak signals with named observation sources and three kill-signals that would force retraction, plus a review date. - Use Case: A product team debating whether to wait for on-device LLM inference gets a dated prediction (e.g., ">50% of new enterprise summarisation deployments on-device by 2027-06-30, confidence 0.65, directional"), the signals to watch in procurement portals and release notes, and the events that would retract the call. ## Quick Start Use the foresight skill to turn the question "when will solid-state batteries reach mass-market EVs?" into a dated prediction with accelerants, blockers, weak signals, kill-signals, and a review date.

Frequently Asked Questions about foresight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a falsifiable technology forecast with a date and confidence?▼

Write one sentence with a subject, verb, absolute date, and numeric confidence, then attach three accelerants, three blockers, three weak signals, three kill-signals, and a review date. Confidence between 0.5 and 0.7 is published as directional; below 0.5 it is written as an open question instead.

What is the difference between foresight prediction and scenario planning?▼

Foresight produces one dated trajectory for a timing question, while scenario planning builds a 2x2 matrix of branching futures from critical uncertainties. Use scenario planning when the question is "what could happen" and foresight when it is "when will X happen".

What are kill-signals in a forecast and why do they matter?▼

A kill-signal is a specific, publicly observable event sufficient on its own to retract the prediction, such as a vendor publishing a roadmap that rules out the milestone. Without kill-signals and a review date, a forecast is an opinion that no evidence can disturb.

When should I use horizon scanning instead of a single prediction?▼

Use horizon scanning when you need a standing sweep of many emerging issues across sources rather than one dated forecast. Horizon scanning surfaces and prioritizes signals; the foresight skill then tracks a chosen trajectory with dates and kill-signals.

How is forecast accuracy scored after the prediction resolves?▼

The dated prediction is recorded and later scored with Brier score calibration, which decomposes accuracy into calibration and discrimination. Confidence bands are designed to be scoreable so forecasts cannot drift toward optimism unchecked.