Skip to main content
command CX Codex

future-scenario-generator · davepoon — Claude Code command: purpose and setup

future-scenario-generator builds future scenarios from trends and scores how plausible they are. Use it to compare possible outcomes before making a decision.

MIT ★ 3,785 updated 2026-10-25

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add davepoon/buildwithclaude
/plugin install all-commands@buildwithclaude
Open on GitHub

What future-scenario-generator does

The command first checks whether the request gives a time horizon, domain, key variables, and the decision the scenarios should inform. It then explores different trend paths, from steady continuation to reversal or disruption, and combines them into scenario options. When essential context is unclear, it asks follow-up questions.

For plausibility, the framework considers historical parallels, logical consistency, expert judgment, and empirical support. It can also examine uncertainty using confidence intervals, sensitivity analysis, Monte Carlo simulation, and expert probability estimates. Treat the result as an analysis framework, not a ready-made forecast: conclusions depend on the variables and evidence supplied.

To install in Claude Code, add the buildwithclaude marketplace, then install all-commands. The command file is future-scenario-generator.md.

What it helps with

  • compare possible industry outcomes over a chosen horizon
  • explore how a trend could accelerate, stall, or reverse
  • score scenarios against several plausibility criteria
  • test how uncertain assumptions affect a scenario

Example prompts for the agent

  • Generate scenarios for this market over the chosen horizon and identify the main variables.
  • Compare outcomes where the current trend accelerates, slows down, or reverses.
  • Assess how plausible these scenarios are and identify the assumptions that shape the result most.

How to install future-scenario-generator

1Plugin marketplace

/plugin marketplace add davepoon/buildwithclaude
/plugin install all-commands@buildwithclaude

2Manually: put the files in place

.claude/commands/future-scenario-generator.md

Call it with /future-scenario-generator. For all projects use ~/.claude/commands/

Questions about future-scenario-generator

How do I install future-scenario-generator in Claude Code?

Run /plugin marketplace add davepoon/buildwithclaude and then /plugin install all-commands@buildwithclaude.

What does future-scenario-generator do?

It creates future scenarios from trends and evaluates their plausibility. It also offers ways to examine uncertainty in key assumptions.

How does the command handle uncertainty?

It can use confidence intervals, sensitivity analysis, Monte Carlo simulation, and expert estimates of probability.

Source text

future-scenario-generator.md · MIT
---
description: Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.
category: simulation-modeling
argument-hint: "Specify scenario parameters"
allowed-tools: Glob
---

# Future Scenario Generator

Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.

## Instructions

You are tasked with systematically generating comprehensive future scenarios to explore potential developments and prepare for multiple possible futures. Follow this approach: **$ARGUMENTS**

### 1. Prerequisites Assessment

**Critical Scenario Context Validation:**

- **Time Horizon**: What future timeframe are you exploring (1-3-5-10+ years)?
- **Domain Focus**: What specific area/industry/system are you analyzing?
- **Key Variables**: What factors could significantly shape the future?
- **Decision Impact**: How will these scenarios inform specific decisions?
- **Uncertainty Level**: What's the acceptable range of scenario uncertainty?

**If context is unclear, guide systematically:**

```
Missing Time Horizon:
"What future timeframe should we explore?
- Near-term (1-2 years): Market shifts, competitive moves, technology adoption
- Medium-term (3-5 years): Industry transformation, regulatory changes, generational shifts  
- Long-term (5-10+ years): Fundamental technology disruption, societal changes, paradigm shifts

Each timeframe requires different scenario methodologies and uncertainty management."

Missing Domain Focus:
"What specific domain or system should we model future scenarios for?
- Business/Industry: Market evolution, competitive landscape, customer behavior
- Technology: Platform shifts, capability development, adoption patterns
- Society/Culture: Demographic changes, value shifts, behavior evolution
- Economy/Policy: Regulatory changes, economic cycles, political developments"
```

### 2. Trend Analysis Foundation

**Systematically analyze current trends as scenario building blocks:**

#### Trend Identification Framework
```
Multi-Dimensional Trend Analysis:

Technology Trends:
- Emerging technologies and adoption curves
- Infrastructure development and capability expansion
- Platform shifts and ecosystem evolution
- Innovation cycles and breakthrough potential

Social/Cultural Trends:
- Demographic shifts and generational changes
- Value system evolution and priority shifts
- Behavior pattern changes and lifestyle adaptation
- Communication and interaction pattern evolution

Economic Trends:
- Market structure changes and industry evolution
- Investment patterns and capital allocation shifts
- Globalization and trade pattern modifications
- Economic cycle positioning and policy directions

Regulatory/Policy Trends:
- Regulatory environment evolution and compliance requirements
- Policy direction changes and government priorities
- International relations and trade agreement impacts
- Legal framework development and enforcement patterns
```

#### Trend Trajectory Modeling
- Linear progression scenarios (current trends continue)
- Acceleration scenarios (trends speed up dramatically)
- Deceleration scenarios (trends slow down or plateau)
- Reversal scenarios (trends change direction)
- Disruption scenarios (trends are fundamentally altered)

### 3. Scenario Architecture Design

**Structure comprehensive scenario frameworks:**

#### Scenario Generation Methodology
```
Systematic Scenario Construction:

Cross-Impact Analysis:
- Identify key driving forces and variables
- Analyze interaction effects between different trends
- Map reinforcing and conflicting trend combinations
- Model cascade effects and secondary impacts

Morphological Analysis:
- Define key dimensions of future variation
- Identify possible states for each dimension
- Generate scenario combinations systematically
- Evaluate scenario consistency and plausibility

Narrative Scenario Development:
- Create compelling future stories and visions
- Integrate quantitative trends with qualitative insights
- Develop scenario logic and causal narratives
- Ensure scenario diversity and comprehensive coverage
```

#### Scenario Categorization Framework
```
Scenario Portfolio Structure:

Baseline Scenarios (30-40% of portfolio):
- Continuation of current trends with normal variation
- Evolutionary change within existing paradigms
- Moderate uncertainty and predictable development patterns

Optimistic Scenarios (20-25% of portfolio):
- Favorable trend convergence and positive developments
- Breakthrough innovations and acceleration opportunities
- Best-case outcome realization and synergy effects

Pessimistic Scenarios (20-25% of portfolio):
- Adverse trend combinations and negative developments
- Crisis scenarios and system stress conditions
- Worst-case outcome realization and cascade failures

Transformation Scenarios (15-20% of portfolio):
- Paradigm shifts and fundamental system changes
- Disruptive innovation and market restructuring
- Wild card events and black swan developments
```

### 4. Plausibility Assessment Framework

**Systematically evaluate scenario credibility:**

#### Plausibility Scoring Methodology
```
Multi-Criteria Plausibility Assessment:

Historical Precedent (25% weight):
- Similar patterns and developments in historical context
- Analogous situations and outcome patterns
- Learning from past trend evolution and scenario realization

Logical Consistency (25% weight):
- Internal scenario logic and causal relationships
- Consistency between different scenario elements
- Absence of logical contradictions and impossible combinations

Expert Validation (25% weight):
- Domain expert assessment and credibility evaluation
- Stakeholder input and perspective integration
- Professional judgment and experience-based validation

Empirical Support (25% weight):
- Current data and trend evidence supporting scenario elements
- Quantitative model outputs and statistical projections
- Research findings and academic literature support

Plausibility Score = (Historical × 0.25) + (Logical × 0.25) + (Expert × 0.25) + (Empirical × 0.25)
```

#### Uncertainty Quantification
- Confidence intervals for key scenario parameters
- Sensitivity analysis for critical assumptions
- Monte Carlo simulation for probability distributions
- Expert elicitation for subjective probability assessment

### 5. Wild Card and Disruption Modeling

**Incorporate low-probability, high-impact events:**

#### Wild Card Event Framework
```
Systematic Disruption Analysis:

Technology Wild Cards:
- Breakthrough innovations and paradigm shifts
- Technology convergence and unexpected capabilities
- Platform disruptions and ecosystem transformations
- Artificial intelligence and automation breakthroughs

Social Wild Cards:
- Generational value shifts and behavior changes
- Social movement emergence and cultural transformations
- Demographic surprises and migration patterns
- Communication and social interaction disruptions

Economic Wild Cards:
- Financial system disruptions and market structure changes
- Resource scarcity or abundance surprises
- Currency and monetary system transformations
- Trade pattern disruptions and economic bloc changes

Environmental/Political Wild Cards:
- Climate change acceleration or mitigation breakthroughs
- Geopolitical shifts and international relation changes
- Natural disasters and pandemic impacts
- Regulatory surprises and policy paradigm shifts
```

#### Disruption Impact Modeling
- Direct impact assessment on key scenario variables
- Cascade effect analysis through system dependencies
- Adaptation and recovery scenario development
- Resilience and vulnerability analysis

### 6. Scenario Integration and Synthesis

**Combine scenarios into comprehensive future landscape:**

#### Cross-Scenario Analysis
```
Scenario Portfolio Analysis:

Scenario Clustering:
- Group similar scenarios and identify common patterns
- Analyze scenario divergence points and branching factors
- Map scenario transition probabilities and pathways
- Identify robust strategies across multiple scenarios

Scenario Interaction Effects:
- How scenarios might combine or influence each other
- Sequential scenario development and evolution patterns
- Scenario switching triggers and transition indicators
- Portfolio effects of scenario diversification

Key Insight Synthesis:
- Common themes and patterns across scenarios
- Critical uncertainties and decision-relevant factors
- Robust trends that appear in most scenarios
- Strategic implications and opportunity identification
```

#### Scenario Narrative Development
- Compelling future stories that integrate multiple trends
- Character and stakeholder perspective integration
- Timeline development and milestone identification
- Vivid details that make scenarios memorable and actionable

### 7. Decision Integration Framework

**Connect scenarios to actionable strategic insights:**

#### Strategy Testing Against Scenarios
```
Scenario-Based Strategy Evaluation:

Strategy Robustness Analysis:
- How well do current strategies perform across scenarios?
- Which scenarios pose the greatest strategic challenges?
- What strategy modifications improve cross-scenario performance?
- Where are the greatest strategy vulnerabilities and dependencies?

Option Value Analysis:
- What strategic options provide value across multiple scenarios?
- Which investments maintain flexibility for different futures?
- How can strategies be designed for adaptive capability?
- What early warning systems enable strategy adjustment?

Contingency Planning:
- Specific response strategies for different scenario realizations
- Resource allocation across scenarios and strategy options
- Decision trigger identification and monitoring systems
- Implementation readiness for scenario-specific strategies
```

#### Strategic Recommendation Generation
```
Scenario-Informed Strategy Framework:

## Future Scenario Analysis: [Domain/Project Name]

### Scenario Portfolio Summary
- Time Horizon: [analysis period]
- Key Driving Forces: [primary variables analyzed]
- Scenarios Generated: [number and types]
- Plausibility Range: [confidence levels]

### High-Impact Scenarios

#### Scenario 1: [Name - Plausibility Score]
- Timeline: [key development milestones]
- Driving Forces: [primary trends and factors]
- Key Characteristics: [distinctive features]
- Strategic Implications: [decision impacts]

[Repeat for top 4-6 scenarios]

### Cross-Scenario Insights
- Robust Trends: [patterns appearing in most scenarios]
- Critical Uncertainties: [factors determining scenario outcomes]
- Strategic Vulnerabilities: [areas of risk across scenarios]
- Opportunity Convergence: [areas of opportunity across scenarios]

### Strategic Recommendations
- Core Strategy: [approach that works across multiple scenarios]
- Scenario-Specific Tactics: [adaptations for different scenarios]
- Early Warning Indicators: [signals for scenario realization]
- Strategic Options: [investments that maintain flexibility]

### Monitoring and Adaptation Framework
- Key Indicators: [metrics to track scenario development]
- Decision Triggers: [when to adjust strategy based on signals]
- Contingency Plans: [specific responses for different scenarios]
- Review Schedule: [when to update scenario analysis]
```

### 8. Continuous Scenario Evolution

**Establish ongoing scenario refinement and updating:**

#### Real-World Validation
- Track actual developments against scenario predictions
- Update scenario probabilities based on emerging evidence
- Refine scenario assumptions based on real-world feedback
- Learn from scenario accuracy and prediction quality

#### Adaptive Scenario Management
- Regular scenario refresh and update cycles
- New information integration and scenario modification
- Stakeholder feedback incorporation and perspective updates
- Methodology improvement based on scenario performance

## Usage Examples

```bash
# Industry transformation scenarios
/simulation:future-scenario-generator Generate scenarios for AI's impact on healthcare industry over next 10 years

# Technology adoption scenarios
/simulation:future-scenario-generator Model future scenarios for remote work technology adoption and workplace evolution

# Market evolution scenarios  
/simulation:future-scenario-generator Explore scenarios for sustainable energy market development and regulatory changes

# Competitive landscape scenarios
/simulation:future-scenario-generator Generate scenarios for fintech industry evolution and traditional banking disruption
```

## Quality Indicators

- **Green**: Diverse scenario portfolio, validated plausibility scores, integrated wild cards
- **Yellow**: Good scenario variety, reasonable plausibility assessment, some disruption modeling
- **Red**: Limited scenario diversity, unvalidated assumptions, missing disruption analysis

## Common Pitfalls to Avoid

- Present bias: Projecting current conditions too strongly into the future
- Linear thinking: Assuming trends continue unchanged without acceleration or disruption
- Probability illusion: Being overconfident in specific scenario likelihoods
- Complexity underestimation: Not modeling interaction effects between trends
- Wild card blindness: Ignoring low-probability, high-impact events
- Action paralysis: Generating scenarios without connecting to decisions

Transform uncertainty into strategic advantage through systematic future scenario exploration and preparation.

© BuildWithClaude Community · MIT · davepoon/buildwithclaude

Similar slash commands

Slash commands catalog →

future-scenario-generator by other authors comes first.

future-scenario-generator davila7 future-scenario-generator builds scenarios for a chosen time horizon, scores their plausibility, and connects them to strategic decisions. Use it to explore risks and possible outcomes. CX Codex +1 222installs future-agi-platform reason-machines future-agi-platform — a skill that walks your coding agent through Future AGI: wiring up tracing, running eval metrics, and self-hosting the platform. CX Codex +1 315installs Future Video Studio ar1adn3c01l Future Video Studio is an MCP server for Claude Code that sends screenplay-style briefs and media assets into video production. The agent can track or cancel renders and download finished videos. CX Codex +1 246installs architecture-scenario-explorer davila7 architecture-scenario-explorer walks an agent through architecture choices under load, growth and failure scenarios, then lays out the trade-offs between quality attributes. CX Codex +1 423installs business-scenario-explorer davila7 business-scenario-explorer — a slash command that maps out several business timelines — baseline, optimistic, pessimistic and disruption — and turns them into a decision matrix. CX Codex +1 273installs scenario-analyzer tradermonty scenario-analyzer turns a news headline into three 18-month scenarios, with sector impacts and a stock list, then has a second agent review it. CX Codex +1 3,800installs test-scenario Owl-Listener Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,400installs

From the same set235

The whole set →
estimate-assistant estimate-assistant calculates project delivery estimates from commit history, PR turnaround times, and code complexity metrics. CX Codex +1 ★ 3,785repo stars gsd:reapply-patches gsd:reapply-patches is a Claude Code skill that carries local GSD changes into the installed version after an update. It handles updates that replaced customized files. CX Codex +1 ★ 3,785repo stars twitter-algorithm-optimizer twitter-algorithm-optimizer — a skill for Claude Code and Cursor that rewrites tweets to match X ranking algorithms so your post reaches more followers and non-followers. CX Codex +1 ★ 3,785repo stars gitlab-automation gitlab-automation automates GitLab project tasks, issue tracking, merge requests, branch operations, and CI/CD pipelines through Rube MCP. CX Codex +1 ★ 3,785repo stars decision-quality-analyzer decision-quality-analyzer scores how a team reaches a decision: four quality axes, a bias sweep, and scenario runs on past and hypothetical calls. CX Codex +1 ★ 3,785repo stars hypotheses-manager hypotheses-manager evaluates startup hypotheses against interview evidence using backlinks and returns the smallest next validation move. Runs via the main agent. CX Codex ★ 3,785repo stars gsd-integration-checker The gsd-integration-checker subagent traces connections between project phases and follows user journeys through the code. Use it to spot broken wiring that a component-by-component review can miss. CX Codex ★ 3,785repo stars gsd-ui-researcher gsd-ui-researcher — a subagent that reads requirements and project context, detects design system state, and produces UI-SPEC.md—a design contract document for frontend phases. Invoked by the /gsd:ui-phase orchestrator. CX Codex ★ 3,785repo stars

Project sponsors

Companies that keep this analytics open