boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Explore decision branches with probability weighting, expected value analysis, and scenario-based optimization.
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/decision-tree-explorerContext preview
What this command does when you run it.
Explore decision branches with probability weighting, expected value analysis, and scenario-based optimization.
Explore decision branches with probability weighting, expected value analysis, and scenario-based optimization.
You are tasked with creating a comprehensive decision tree analysis to explore complex decision scenarios and optimize choice outcomes. Follow this systematic approach: **$ARGUMENTS**
**Critical Decision Context Validation:**
**If any context is unclear, guide systematically:**
Missing Decision Scope: "I need clarity on the decision you're analyzing. Please specify: - Primary Decision: The main choice you need to make - Decision Level: Strategic, tactical, or operational - Decision Type: Go/no-go, resource allocation, priority ranking, or option selection - Alternative Options: What choices are you considering? Examples: - Strategic: 'Should we enter the European market next year?' - Investment: 'Which of 3 product features should we build first?' - Operational: 'Should we migrate to microservices or improve the monolith?' - Crisis: 'How should we respond to the new competitor launch?'" Missing Success Criteria: "How will you evaluate if this decision was successful? - Financial Metrics: Revenue impact, cost savings, ROI targets - Strategic Metrics: Market share, competitive position, capability building - Operational Metrics: Efficiency gains, quality improvements, risk reduction - Timeline Metrics: Speed to market, implementation time, payback period" Missing Resource Context: "What constraints limit your decision options? - Budget: Available investment capital and operating funds - Time: Implementation deadlines and resource availability windows - Capabilities: Team skills, technology infrastructure, operational capacity - Regulatory: Compliance requirements and approval processes"
**Structure the decision systematically:**
**Systematically identify and organize decision alternatives:**
For each option, evaluate: - Technical Feasibility: Can this actually be implemented? - Economic Feasibility: Do benefits justify costs? - Operational Feasibility: Do we have capability to execute? - Timeline Feasibility: Can this be done in available time? - Political Feasibility: Will stakeholders support this? Feasibility Scoring (1-10 scale): Option: [name] - Technical: [score] - [reasoning] - Economic: [score] - [reasoning] - Operational: [score] - [reasoning] - Timeline: [score] - [reasoning] - Political: [score] - [reasoning] Overall Feasibility: [average score]
**Apply systematic probability estimation:**
Use multiple estimation approaches: 1. Historical Data Analysis: - Similar past decisions and outcomes - Success/failure rates in comparable situations - Market adoption patterns for similar offerings 2. Expert Consultation: - Domain expert probability estimates - Cross-functional team input and perspectives - External advisor and consultant insights 3. Market Validation: - Customer research and feedback - Competitive analysis and market dynamics - Regulatory and environmental factor assessment 4. Monte Carlo Simulation: - Run multiple probability scenarios - Test sensitivity to assumption changes - Generate confidence intervals for estimates
**Quantify decision outcomes systematically:**
##
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:…