boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/project-timeline-simulatorContext preview
What this command does when you run it.
Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.
Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.
You are tasked with creating comprehensive project timeline simulations to optimize planning, resource allocation, and risk management. Follow this approach: **$ARGUMENTS**
**Critical Project Context Validation:**
**If context is unclear, guide systematically:**
Missing Project Scope: "What type of project needs timeline simulation? - Software Development: Feature development, platform migration, system redesign - Product Launch: New product development from concept to market - Business Initiative: Process improvement, organizational change, market expansion - Infrastructure Project: System upgrades, tool implementation, capacity expansion Please specify project deliverables, stakeholders, and success criteria." Missing Key Variables: "What factors could significantly impact your project timeline? - Resource Availability: Team capacity, skill availability, external dependencies - Technical Complexity: Unknown requirements, integration challenges, performance needs - External Dependencies: Vendor deliveries, regulatory approvals, partner coordination - Market Dynamics: Customer feedback, competitive pressure, business priority changes"
**Systematically map project components and dependencies:**
Project Component Framework: Phase-Based Structure: - Discovery/Planning: Requirements gathering, design, architecture planning - Development/Implementation: Core building, integration, testing phases - Validation/Testing: Quality assurance, user acceptance, performance validation - Deployment/Launch: Release preparation, rollout, go-live activities - Stabilization/Optimization: Post-launch support, performance tuning, iteration Feature-Based Structure: - Core Features: Essential functionality for minimum viable product - Enhanced Features: Additional capabilities for competitive advantage - Integration Features: System connectivity and data synchronization - Quality Features: Security, performance, reliability, and maintainability Skill-Based Structure: - Frontend Development: User interface and experience implementation - Backend Development: Server logic, APIs, and data processing - Infrastructure/DevOps: Deployment, monitoring, and operational setup - Design/UX: User research, interface design, and usability testing - Quality Assurance: Testing strategy, automation, and validation
Project Dependency Analysis: Sequential Dependencies: - Finish-to-Start: Task B cannot begin until Task A completes - Start-to-Start: Task B cannot start until Task A has started - Finish-to-Finish: Task B cannot finish until Task A finishes - Start-to-Finish: Task B cannot finish until Task A starts Resource Dependencies: - Shared Resources: Team members working across multiple tasks - Skill Dependencies: Specialized expertise required for specific tasks - Tool Dependencies: Software, hardware, or platform availability - Budget Dependencies: Funding approval and expenditure timing External Dependencies: - Vendor Deliveries: Third-party software, services, or hardware - Regulatory Approvals: Compliance reviews and certification processes - Stakeholder Decisions: Business approvals and priority setting - Market Timing: Customer readiness and competitive positioning
**Systematically model factors affecting timeline outcomes:**
Timeline Variable Categories: Effort Estimation Variables: - Task Complexity: Simple, moderate, complex, or unknown complexity - Team Experience: Expert, experienced, moderate, or novice skill levels - Requirements Clarity: Well-defined, partially defined, or evolving requirements - Technology Maturity: Proven, established, emerging, or experimental technology Resource Variables: - Team Availability: Full-time, part-time, or shared allocation percentages - Skill Availability: In-house expertise, contractors, or training requirements - Infrastructure Readiness: Available, partially ready, or needs development - Budget Flexibility: Fixed, constrained, or adjustable funding levels External Variables: - Stakeholder Responsiveness: Fast, normal, or slow decision and feedback cycles - Market Stability: Stable, evolving, or rapidly changing requirements - Regulatory Environment: Clear, evolving, or uncertain compliance landscape - Competitive Pressure: Low, moderate, or high urgency for delivery
Probabilistic Timeline Estimation: Three-Point Estimation: - Optimistic Estimate: Best-case scenario with favorable conditions - Most Likely Estimate: Expected scenario with normal conditions - Pessimistic Estimate: Worst-case scenario with adverse conditions Distribution Types: - PERT Distribution: Beta distribution weighted toward most likely - Triangular Distribution: Linear probability between min, mode, max - Normal Distribution: Bell curve around mean with standard deviation - Log-Normal Distribution: Right-skewed for tasks with uncertainty Monte Carlo Simulation: - Random sampling from variable distributions - Thousands of simulation runs for statistical analysis - Confidence intervals for timeline predictions - Risk quantification and probability assessment
**Create comprehensive project timeline scenarios:**
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:…