Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Shell Method Scenario Planning

ASecurity

Navigate strategic uncertainty through multiple plausible future scenarios rather than single-point forecasting. Developed at Royal Dutch Shell, this framework replaces single-point predictions with 2-4 rich narratives representing genuinely different futures defined by critical uncertainties.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
businessgoshellawstestingapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill shell-method-scenario-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Shell Method Scenario Planning?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Shell Method Scenario Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-shell-method-scenario-planning/badge)](https://www.skillsdirectory.com/skills/lev-os-shell-method-scenario-planning)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: shell-method-scenario-planning
description: Navigate strategic uncertainty through multiple plausible future scenarios rather than single-point forecasting. Developed at Royal Dutch Shell, this framework replaces single-point predictions with 2-4 rich narratives representing genuinely different futures defined by critical uncertainties.
---

# Shell Method (Scenario Planning)

## Purpose

The Shell Method is a scenario planning framework for navigating long-term strategic uncertainty. Rather than predicting "the" future, create 2-4 rich narratives representing genuinely different future states. This approach enables identification of robust strategies that work across multiple futures and contingent strategies for specific scenarios.

**Historical validation**: Successfully predicted the 1973 oil crisis, enabling Shell to rise from 7th to 2nd largest oil company while competitors operated on business-as-usual assumptions.

## When to Use This Skill

This skill should be used when:

- **Facing strategic uncertainty at 5-30 year horizons** - When long-term planning is needed and experts disagree about critical factors
- **Single forecasts prove unreliable** - When business-as-usual assumptions are being challenged by emerging uncertainties
- **High-stakes decisions with irreversible commitments** - When major investments or strategic pivots require stress-testing against multiple futures
- **Experts fundamentally disagree** - When domain experts provide conflicting predictions or data conflicts emerge
- **Industry disruption is possible** - When technological, regulatory, or market shifts could fundamentally reshape the competitive landscape
- **Need shared organizational mental models** - When coordinated response is required without central command during uncertainty

**Semantic triggers**: "scenario planning", "strategic foresight", "multiple futures", "uncertainty mapping", "long-term strategy", "what-if analysis for strategy"

## Core Approach

**Central distinction**: Separate "predetermined elements" (high-confidence trends like demographics, infrastructure, enacted laws) from "critical uncertainties" (high-impact unknowns where experts disagree).

**Key insight**: Map uncertainties on a 2×2 matrix and develop narrative scenarios for each quadrant to identify:
- **No-regret moves**: Strategies that work across all futures
- **Contingent moves**: Actions triggered by specific scenario indicators

## Process

### Step 1: Identify Focal Question

Define the strategic decision and planning horizon:

1. **Set planning horizon** - Typically 5-30 years for strategic uncertainty
2. **List critical unknowns** - Technologies, regulations, competitors, customer behavior
3. **Frame as focal question** - "What should our strategy be given [uncertainty]?"

**Questions to answer**:
- What strategic decision are we facing?
- What do we need to know but don't?
- What uncertainties could make or break our strategy?

**Example**: Shell 1971: "How should we position ourselves given potential energy supply disruptions and price volatility over the next 10 years?"

### Step 2: Research Elements and Uncertainties

Separate what is known from what is genuinely uncertain:

1. **Identify predetermined elements** - Trends with high confidence (demographics, infrastructure momentum, laws already passed)
2. **Identify critical uncertainties** - High-impact factors where experts disagree or data conflicts
3. **Interview domain experts** - Analyze data, identify divergent viewpoints
4. **Test for genuine uncertainty** - If experts agree, it's predetermined; if they disagree, it's uncertain

**Deliverables**:
- List of predetermined elements ("We know...")
- List of critical uncertainties ("We don't know...")

**Example**: Shell 1971 - Predetermined: Oil production has physical limits, demand growing. Uncertain: When will supply/demand cross? How will governments respond?

### Step 3: Select Two Critical Uncertainties

Choose two independent uncertainties for a 2×2 matrix:

1. **Rank uncertainties** - By strategic impact and unpredictability
2. **Select two independent factors** - Not correlated with each other
3. **Define clear endpoints** - For each axis (e.g., "Loose regulation" vs "Tight regulation")
4. **Validate quadrants** - Ensure four distinct, meaningful future states

**Quality checks**:
- Are these uncertainties genuinely unpredictable (not just unknown)?
- Are the two axes independent of each other?
- Do the four quadrants represent meaningfully different futures?

**Output**: 2×2 matrix with four quadrants representing distinct future states

**Example**: Shell - Axis 1: Oil prices (low vs high), Axis 2: Government intervention (minimal vs heavy)

### Step 4: Develop Rich Narratives

Create detailed stories for how each quadrant future unfolds:

1. **Write 3-5 page narrative for each quadrant**
2. **Include causal chains** - Triggering events, stakeholder responses, second-order effects
3. **Give memorable names** - e.g., "Wild West", "Regulated Utility", "Climate Crisis"
4. **Use storytelling techniques** - Make vivid, coherent, plausible
5. **Ensure internal consistency** - Each scenario must pass logical scrutiny

**Story elements**:
- What event could trigger this future?
- How would key stakeholders respond?
- What second-order effects cascade from initial changes?
- What does daily life/business look like in this future?

**Output**: 2-4 detailed scenario narratives (3-5 pages each) with memorable names

**Example**: Shell 1973 Type A scenario: Technical extraction limits → supply shortage → price spike → economic shock → geopolitical realignment

### Step 5: Test Strategy Against Scenarios

Evaluate current and alternative strategies across all scenarios:

1. **Identify current strategy assumptions** - What future is the current plan betting on?
2. **Stress-test across scenarios** - How does current strategy perform in each quadrant?
3. **Identify vulnerabilities** - Which scenarios break the current strategy?
4. **Design strategy variants** - Create alternatives optimized for different scenarios

**Analysis questions**:
- Does our current strategy only work in one scenario?
- Which scenarios would cause strategic failure?
- What early indicators would signal which scenario is unfolding?

**Output**: Strategy vulnerability analysis across scenarios

### Step 6: Develop Robust and Contingent Strategies

Design strategies that account for multiple futures:

1. **Identify no-regret moves** - Actions that improve outcomes across ALL scenarios
2. **Design contingent strategies** - Moves triggered when specific scenarios unfold
3. **Define leading indicators** - Metrics that signal which scenario is materializing
4. **Establish decision triggers** - Conditions that activate contingent strategies
5. **Monitor for scenario shifts** - Ongoing surveillance for early warning signals

**Strategy types**:
- **Robust/no-regret**: Invest in adaptive capacity, diversification, scenario monitoring systems
- **Contingent**: Pre-plan responses but delay execution until scenario clarity emerges

**Deliverables**:
- List of no-regret moves (execute now)
- List of contingent strategies (execute if scenario X unfolds)
- Dashboard of leading indicators
- Decision triggers for strategy pivots

**Example**: Shell post-1973 - No-regret: Build scenario planning capability. Contingent: If supply constraints emerge, pre-position for scarcity market.

## Practical Techniques

### Technique 1: Type A vs Type B Scenarios

**Purpose**: Distinguish between psychological reframing and genuine uncertainty exploration.

**Process**:
1. **Type A scenarios** - Uncomfortable but plausible futures that challenge business-as-usual mental models
2. **Type B scenarios** - Variations on current trends (less transformative)
3. **Focus on Type A** - These provide the most strategic value by breaking groupthink

**Example**: Shell's Type A (supply crisis) vs Type B (steady growth continuation)

### Technique 2: Predetermined Elements Filter

**Purpose**: Avoid treating known trends as uncertainties.

**Process**:
1. List all factors affecting the focal question
2. Test each: "Do credible experts disagree fundamentally?"
3. If NO → Predetermined element (incorporate into all scenarios)
4. If YES → Critical uncertainty (becomes scenario differentiator)

**Benefit**: Reduces scenario complexity by removing false uncertainties

### Technique 3: Early Warning Indicator System

**Purpose**: Detect which scenario is materializing as the future unfolds.

**Process**:
1. For each scenario, identify unique leading indicators
2. Monitor these indicators monthly/quarterly
3. When multiple indicators align, activate contingent strategy
4. Update scenarios annually as predetermined elements increase

**Example**: Monitoring oil inventory levels, OPEC statements, alternative energy investment as signals

## Common Pitfalls

Avoid these anti-patterns:

1. **Probability assignment** - Do NOT assign probabilities to scenarios; maintains openness to surprises
2. **Best/worst/baseline framing** - Creates confirmation bias toward baseline; use neutral names
3. **Too many scenarios** - 2-4 is optimal; more creates analysis paralysis
4. **Single-variable scenarios** - Need at least two independent uncertainties for richness
5. **Insufficient narrative detail** - Thin scenarios don't change mental models; aim for 3-5 pages each
6. **No strategy implications** - Scenarios without strategic testing are just stories; must drive decisions

## Integration

**Complements**:
- Pre-mortem analysis (test strategy failures in each scenario)
- OODA loop (rapid adaptation when scenario signals emerge)
- Red team/blue team exercises (stress-test scenario narratives)
- Strategic roadmapping (timeline no-regret vs contingent moves)

**Conflicts with**:
- Single-point forecasting methodologies
- Deterministic planning approaches
- Short-term optimization frameworks

**Leads to**:
- Dynamic strategy portfolios
- Adaptive capacity building
- Resilience-oriented decision-making

## Time Estimates

**Full process**: 3-6 months for comprehensive organizational scenario planning
**Rapid sprint**: 1-2 weeks for simplified scenario exploration
**Annual refresh**: 1-2 weeks to update scenarios and indicators

**Complexity**: High - Requires cross-functional input, expert interviews, and organizational buy-in

## Reference

**Authors**: Pierre Wack, Ted Newland, Peter Schwartz (Royal Dutch Shell, 1960s-1990s)

**Category**: Strategic foresight, decision-making under uncertainty

**Historical context**: Developed at Royal Dutch Shell to navigate oil industry volatility, gained legendary status after predicting 1973 oil crisis.

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Solution Architect

Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

192 votes

Akorchak:Venture Assessment

Generate a comprehensive VC investment assessment report for a company

72 votes

Stock Analysis

Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management (create, add, remove assets), crypto analysis (Top 20 by market cap), and periodic performance reports (daily/weekly/monthly/quarterly/yearly). 8 analysis dimensions for stocks, 3 for crypto. Use for stock analysis, portfolio tracking, earnings reactions, or crypto monitoring.

6511 votes

Just Fucking Cancel

Find and cancel unwanted subscriptions by analyzing bank transactions. Detects recurring charges, calculates annual waste, and helps you cancel with direct URLs and browser automation. Use when: 'cancel subscriptions', 'audit subscriptions', 'find recurring charges', 'what am I paying for', 'save money', 'subscription cleanup', 'stop wasting money'. Supports CSV import (Apple Card, Chase, Amex, Citi, Bank of America, Capital One, Mint, Copilot) OR Plaid API for automatic transaction pull. Out...

6511 votes

Telegram Compose

Compose rich, readable Telegram messages using HTML formatting via direct Telegram API. Use when: (1) Sending any Telegram message beyond a simple one-line reply, (2) Creating structured messages with sections, lists, or status updates, (3) Need formatting unavailable via Clawdbot's Markdown conversion (underline, spoilers, expandable blockquotes, user mentions by ID), (4) Sending alerts, reports, summaries, or notifications to Telegram, (5) Want professional, scannable message formatting wit...

6511 votes
View all in business →