backcasting

Builds a dated milestone chain backwards from a desired end state to the present.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a goal is set that current trends will not deliver — net-zero by 2040, a 2035 business vision — forward planning from today's constraints only extends today's trajectory. This Skill applies Robinson's normative backcasting method (Energy Policy, 1982) to reason backwards from a fixed, quantified end state, exposing the discontinuities, lead times, and lock-ins that a forward plan would hide. ## Core Features & Use Cases - Quantified end state and backward milestone chain: Defines the vision with at least five quantified indicators, then iterates "what must already be true N years earlier?" back to the present, paced by physical and institutional lead times. - Evidenced measure packages and gap analysis: Attaches policies, investments, and precedents to every leg, requires a precedent or owned research bet for each flagged discontinuity, and runs a barrier and lock-in register against the current trajectory. - Near-term action agenda: Produces actions with owners and start dates, decision points that keep two pathways alive, and a review cadence with a re-backcast trigger. - Use Case: A city committed to a zero-emission bus fleet by 2040 uses the Skill to discover that the 12-year bus service life forces the last diesel purchase in 2028, which forces depot upgrade contracts years earlier — constraints invisible in a forward plan. ## Quick Start Use the backcasting skill to work backwards from our 2040 net-zero target into a dated milestone roadmap with near-term actions.

Frequently Asked Questions about backcasting

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

FAQPage Schema
How do I build a roadmap backwards from a long-term target?▼

Backcasting fixes the desired end state first, then iterates "what must already be true N years earlier?" back to the present. Each milestone is dated, lists dependencies, and is paced by physical lead times like asset replacement cycles and permitting rather than planning convenience.

What is the difference between backcasting and forecasting?▼

Forecasting asks what is likely to happen by extrapolating current trends; backcasting asks what would have to happen for a chosen future to be reachable. Backcasting is normative, not predictive, and suits problems where dominant trends are part of the problem.

When should I use scenario planning instead of backcasting?▼

Use scenario planning when the question is which futures could occur or when no one holds the mandate to define the desirable end state. Once a future is chosen, backcast from it to build the pathway; the two methods are complementary, not competing.

How many quantified indicators does a backcasting vision need?▼

The method requires at least five quantified indicators with target values that are simultaneously achievable. Adjectives cannot be backcast from, so the indicator rule is the discipline that keeps the vision concrete rather than a slogan.

What are common failure modes in a backcasting roadmap?▼

Common failures include early milestones that are current projects renamed, discontinuities with no precedent or owner, hard work back-loaded past the leadership horizon, and a single pathway with no decision points. The gap and lock-in analysis step exists to catch these.