constraint-identifier
System bottleneck identification and exploitation skill with throughput analysis and five focusing steps implementation
What this skill does
# Constraint Identifier
## Overview
The Constraint Identifier skill provides comprehensive capabilities for identifying and exploiting system constraints using Theory of Constraints (TOC) principles. It supports bottleneck identification, throughput analysis, and implementation of the five focusing steps.
## Capabilities
- Bottleneck identification algorithms
- Throughput rate analysis
- Constraint exploitation strategies
- Subordination planning
- Buffer sizing calculation
- Constraint elevation options
- Drum identification
## Used By Processes
- TOC-001: Constraint Identification and Exploitation
- TOC-002: Drum-Buffer-Rope Scheduling
- CAP-001: Capacity Requirements Planning
## Tools and Libraries
- Simulation software
- Throughput analysis tools
- Process mapping tools
- Data analytics platforms
## Usage
```yaml
skill: constraint-identifier
inputs:
process_steps:
- name: "Cutting"
capacity: 120
demand: 100
- name: "Assembly"
capacity: 80
demand: 100
- name: "Testing"
capacity: 110
demand: 100
- name: "Packing"
capacity: 150
demand: 100
current_throughput: 78
target_throughput: 100
outputs:
- constraint_identification
- exploitation_strategies
- subordination_plan
- elevation_options
- buffer_recommendations
```
## Five Focusing Steps
### Step 1: Identify the Constraint
- Analyze capacity vs. demand at each step
- Look for WIP accumulation points
- Identify resource with lowest throughput
### Step 2: Exploit the Constraint
- Ensure constraint never starves or blocks
- Eliminate waste at constraint
- Maximize constraint utilization
### Step 3: Subordinate Everything Else
- Pace non-constraints to constraint
- Implement pull system from constraint
- Don't overproduce at non-constraints
### Step 4: Elevate the Constraint
- Add capacity at constraint
- Reduce setup time
- Improve quality at constraint
### Step 5: Prevent Inertia
- Return to Step 1
- Find new constraint
- Continue improvement cycle
## Constraint Types
| Type | Description | Examples |
|------|-------------|----------|
| Physical | Resource limitation | Machine capacity, labor |
| Policy | Rule-based limitation | Batch sizes, schedules |
| Market | Demand limitation | Customer orders |
| Supplier | Input limitation | Raw material availability |
## Integration Points
- Manufacturing Execution Systems
- ERP systems
- Simulation software
- Production planning systems
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.