thinking-theory-of-constraints
Identify and manage the bottleneck; improvements elsewhere don't matter until the constraint is addressed. Use for performance optimization, process improvement, and resource allocation.
Profile →npx skills add majiayu000/claude-skill-registry --skill thinking-theory-of-constraints --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Theory of Constraints ## Overview The Theory of Constraints (TOC), developed by Eliyahu Goldratt in "The Goal," states that every system has exactly one constraint that limits its throughput. Optimizing anything other than the constraint is wasted effort—even counterproductive. Find the bottleneck, exploit it, subordinate everything else to it, and only then consider elevating it. **Core Principle:** A chain is only as strong as its weakest link. Strengthening any other link does nothing. ## When to Use - Performance optimization (systems, processes, teams) - Process improvement - Resource allocation - Throughput analysis - Project management - Capacity planning - Any optimization effort Decision flow: ``` Trying to improve throughput? → Have you identified the constraint? → no → FIND THE CONSTRAINT FIRST → Are you optimizing a non-constraint? → yes → STOP, FOCUS ON CONSTRAINT → Is the constraint working at 100%? → no → EXPLOIT BEFORE ELEVATING ``` ## The Five Focusing Steps ### Step 1: Identify the Constraint Find the one thing limiting the system: ```markdown ## Constraint Identification System: Software delivery pipeline Potential constraints: | Stage | Capacity | Utilization
- Overview
- When to Use
- The Five Focusing Steps
- Step 1: Identify the Constraint
- Step 2: Exploit the Constraint
- Step 3: Subordinate Everything Else
- Step 4: Elevate the Constraint
- Step 5: Prevent Inertia (Go Back to Step 1)
- Finding Constraints
- Types of Constraints
- Constraint Indicators
- TOC Application Patterns
- Performance Optimization
- Team Productivity
What does the thinking-theory-of-constraints skill do?
Identify and manage the bottleneck; improvements elsewhere don't matter until the constraint is addressed. Use for performance optimization, process improvement, and resource allocation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill thinking-theory-of-constraints --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.