skills/hypotheticals-counterfactuals/SKILL.md
Applies "what if" thinking to explore alternative scenarios, test assumptions, understand causal relationships, and prepare for uncertainty. Guides through counterfactual reasoning, scenario exploration, pre-mortem analysis, and stress testing decisions against alternative futures. Use when exploring alternative scenarios, testing assumptions through "what if" questions, understanding causal relationships, conducting pre-mortem analysis, stress testing decisions, or when user mentions counterfactuals, hypothetical scenarios, thought experiments, alternative futures, what-if analysis, or needs to challenge assumptions.
npx skillsauth add lyndonkl/claude hypotheticals-counterfactualsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Copy this checklist and track your progress:
Hypotheticals & Counterfactuals Progress:
- [ ] Step 1: Define the focal question
- [ ] Step 2: Generate counterfactuals or scenarios
- [ ] Step 3: Develop each scenario
- [ ] Step 4: Identify implications and insights
- [ ] Step 5: Extract actions or decisions
- [ ] Step 6: Monitor and update
Step 1: Define the focal question
What are you exploring? Past decision (counterfactual)? Future possibility (hypothetical)? Assumption to test? See resources/template.md.
Step 2: Generate counterfactuals or scenarios
Counterfactual: Change one key factor, ask "what would have happened?" Hypothetical: Imagine future scenarios (2-4 plausible alternatives). See resources/template.md and resources/methodology.md.
Step 3: Develop each scenario
Describe what's different, trace implications, identify key assumptions. Make it vivid and concrete. See resources/template.md and resources/methodology.md.
Step 4: Identify implications and insights
What does each scenario teach? What assumptions are tested? What risks revealed? See resources/methodology.md.
Step 5: Extract actions or decisions
What should we do differently based on these scenarios? Hedge against downside? Prepare for upside? See resources/template.md.
Step 6: Monitor and update
Track which scenario is unfolding. Update plans as reality diverges from expectations. See resources/methodology.md.
Validate using resources/evaluators/rubric_hypotheticals_counterfactuals.json. Minimum standard: Average score ≥ 3.5.
Pattern 1: Pre-Mortem (Prospective Hindsight)
Pattern 2: Counterfactual Causal Analysis
Pattern 3: Three Scenarios (Optimistic, Baseline, Pessimistic)
Pattern 4: 2×2 Scenario Matrix
Pattern 5: Assumption Reversal
Pattern 6: Stress Test (Extreme Scenarios)
Key requirements:
Plausibility constraint: Scenarios must be possible, not just imaginable. "What if gravity reversed?" is not useful counterfactual. Stay within bounds of plausibility given current knowledge.
Minimal rewrite principle (counterfactuals): Change as little as possible. "What if we had chosen Y instead of X?" not "What if we had chosen Y and market doubled and competitor failed?" Isolate causal factor.
Avoid hindsight bias: Pre-mortem assumes failure, but don't just list things that went wrong in similar past failures. Generate new failure modes specific to this context.
Specify mechanism: Don't just state outcome ("sales would be higher"), explain HOW ("sales would be higher because lower price → higher conversion → more customers despite lower margin").
Assign probabilities (scenarios): Don't treat all scenarios as equally likely. Estimate rough probabilities (e.g., 60% baseline, 25% pessimistic, 15% optimistic). Avoids equal-weight fallacy.
Time horizon clarity: Specify WHEN in future. "Product fails" is vague. "In 6 months, adoption <1000 users" is concrete. Enables tracking.
Extract actions, not just stories: Scenarios are useless without implications. Always end with "so what should we do?" Prepare, hedge, pivot, or double-down.
Update scenarios: Reality evolves. Quarterly review: which scenario is unfolding? Update probabilities and plans accordingly.
Common pitfalls:
Counterfactual vs. Hypothetical:
| Type | Direction | Question | Purpose | Example | |------|-----------|----------|---------|---------| | Counterfactual | Backward (past) | "What would have happened if...?" | Understand causality, learn from past | "What if we had launched in EU first?" | | Hypothetical | Forward (future) | "What could happen if...?" | Explore futures, prepare for uncertainty | "What if competitor launches free tier?" |
Scenario types:
| Type | # Scenarios | Structure | Best For | |------|-------------|-----------|----------| | Three scenarios | 3 | Optimistic, Baseline, Pessimistic | General forecasting, strategic planning | | 2×2 matrix | 4 | Two uncertainties create quadrants | Exploring interaction of two drivers | | Cone of uncertainty | Continuous | Range widens over time | Long-term planning (5-10 years) | | Pre-mortem | 1 | Imagine failure, list causes | Risk identification before launch | | Stress test | 2-4 | Extreme scenarios (best/worst) | Decision robustness testing |
Pre-mortem process (6 steps):
2×2 Scenario Matrix (example):
Uncertainties: (1) Market adoption rate, (2) Regulatory environment
| | Slow Adoption | Fast Adoption | |---------------------|---------------|---------------| | Strict Regulation | "Constrained Growth" | "Regulated Scale" | | Loose Regulation | "Patient Build" | "Wild West Growth" |
Assumption reversal questions:
Inputs required:
Outputs produced:
counterfactual-analysis.md: Alternative history analysis with causal insightspre-mortem-risks.md: List of potential failure modes and mitigationsscenarios.md: 2-4 future scenarios with narratives and implicationsaction-plan.md: Decisions and preparations based on scenario insightstesting
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
development
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
development
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
development
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.