capacity-constraint-analyzer
Production capacity analysis skill using Theory of Constraints principles
What this skill does
# Capacity Constraint Analyzer
## Overview
The Capacity Constraint Analyzer provides production and supply chain capacity analysis using Theory of Constraints (TOC) principles. It identifies bottlenecks, models capacity exploitation strategies, and supports capacity investment decisions.
## Capabilities
- **Capacity Utilization Calculation**: Resource utilization analysis
- **Bottleneck Identification**: Constraint and limiting factor detection
- **Constraint Exploitation Strategies**: TOC-based improvement approaches
- **Capacity Adjustment Modeling**: Expansion and contraction scenarios
- **Lead Time Impact Analysis**: Capacity effects on delivery performance
- **Rough-Cut Capacity Planning**: Aggregate capacity assessment
- **Finite Capacity Scheduling Support**: Detailed scheduling inputs
- **Capacity Investment Analysis**: CapEx decision support
## Input Schema
```yaml
capacity_analysis_request:
resources:
work_centers: array
- resource_id: string
name: string
available_capacity: float
capacity_unit: string
efficiency: float
setup_time: float
labor: array
equipment: array
demand_requirements:
production_plan: array
capacity_requirements: array
- resource_id: string
product: string
rate: float
constraints:
operating_hours: object
maintenance_windows: array
policy_limits: object
analysis_parameters:
time_horizon: string
granularity: string
scenarios: array
```
## Output Schema
```yaml
capacity_analysis_output:
utilization_analysis:
by_resource: array
- resource_id: string
name: string
available_capacity: float
required_capacity: float
utilization_percent: float
status: string # under, balanced, constrained, over
summary: object
bottleneck_identification:
constraints: array
- resource_id: string
constraint_type: string
impact: string
root_cause: string
constraint_ranking: array
exploitation_strategies:
recommendations: array
- strategy: string
target_resource: string
expected_improvement: float
implementation_effort: string
capacity_scenarios:
scenarios: array
- scenario_name: string
capacity_changes: object
cost: float
benefit: float
lead_time_impact: string
investment_analysis:
options: array
npv_comparison: object
payback_analysis: object
rough_cut_capacity_plan: object
```
## Usage
### Bottleneck Identification
```
Input: Production plan, resource capacities
Process: Calculate utilization, identify constraints
Output: Bottleneck report with ranking
```
### Capacity Scenario Analysis
```
Input: Demand growth scenarios, current capacity
Process: Model capacity options and impacts
Output: Capacity scenario comparison
```
### TOC Exploitation Strategy
```
Input: Identified constraint, current operations
Process: Apply TOC principles for exploitation
Output: Constraint exploitation recommendations
```
## Integration Points
- **ERP/MES Systems**: Capacity and production data
- **Planning Systems**: Demand and production plans
- **Scheduling Systems**: Finite capacity scheduling
- **Tools/Libraries**: Theory of Constraints frameworks, scheduling algorithms
## Process Dependencies
- Capacity Planning and Constraint Management
- Sales and Operations Planning (S&OP)
- Supply Chain Network Design
## Best Practices
1. Validate capacity data accuracy
2. Consider all constraint types (physical, policy, market)
3. Focus improvement efforts on true constraints
4. Model multiple demand scenarios
5. Include maintenance in capacity calculations
6. Review capacity plans monthly
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.