boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/future-scenario-generatorContext preview
What this command does when you run it.
Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.
Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.
You are tasked with systematically generating comprehensive future scenarios to explore potential developments and prepare for multiple possible futures. Follow this approach: **$ARGUMENTS**
**Critical Scenario Context Validation:**
**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"
**Systematically analyze current trends as scenario building blocks:**
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
**Structure comprehensive scenario frameworks:**
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 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
**Systematically evaluate scenario credibility:**
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)
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles:…