project-timeline-simulator
Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.
What this skill does
# Project Timeline Simulator Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios. ## Instructions You are tasked with creating comprehensive project timeline simulations to optimize planning, resource allocation, and risk management. Follow this approach: **$ARGUMENTS** ### 1. Prerequisites Assessment **Critical Project Context Validation:** - **Project Scope**: What specific project are you simulating timelines for? - **Key Variables**: What factors could significantly impact timeline outcomes? - **Resource Constraints**: What team, budget, and time limitations apply? - **Success Criteria**: How will you measure project success and timeline effectiveness? - **Risk Tolerance**: What level of schedule risk is acceptable? **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" ``` ### 2. Project Structure Modeling **Systematically map project components and dependencies:** #### Work Breakdown Structure (WBS) Analysis ``` 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 ``` #### Dependency Mapping Framework ``` 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 ``` ### 3. Variable Modeling Framework **Systematically model factors affecting timeline outcomes:** #### Uncertainty Factor Analysis ``` 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 ``` #### Variable Distribution Modeling ``` 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 ``` ### 4. Scenario Generation Engine **Create comprehensive project timeline scenarios:** #### Scenario Development Framework ``` Multi-Dimensional Scenario Portfolio: Baseline Scenarios (40% of simulations): - Normal Resource Availability: Team at expected capacity and skills - Standard Complexity: Requirements and technical challenges as anticipated - Typical External Factors: Normal stakeholder responsiveness and market conditions - Expected Dependencies: Third-party deliveries and approvals on schedule Optimistic Scenarios (20% of simulations): - Enhanced Resource Availability: Additional team members or improved productivity - Reduced Complexity: Simpler requirements or technical solutions - Favorable External Factors: Fast stakeholder decisions and stable market - Accelerated Dependencies: Early vendor deliveries and quick approvals Pessimistic Scenarios (25% of simulations): - Constrained Resources: Team availability issues or skill gaps - Increased Complexity: Scope creep or technical challenges - Adverse External Factors: Slow decisions or changing market conditions - Delayed Dependencies: Late vendor deliveries or approval delays Disruption Scenarios (15% of simulations): - Major Scope Changes: Significant requirement modifications mid-project - Team Disruptions: Key team member departures or organizational changes - Technology Disruptions: Platform changes or security requirements - Market Disruptions: Competitive pressure or business priority shifts ``` #### Critical Path Analysis - Identification of activities that directly impact project completion - Float/slack analysis for non-critical activities - Critical path vulnerability assessment under different scenarios - Resource optimization for critical path acceleration ### 5. Risk Assessment and Impact Modeling **Comprehensive project risk evaluation:** #### Risk Identification Framework ``` Project Risk Categories: Technical Risks: - Requirements Risk: Unclear, changing, or conflicting requirements - Technology Risk: Unproven technology or integration challenges - Performance Risk: Scalability, reliabi
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.