菜单
Applies Theory of Constraints methodology to identify bottlenecks and optimize systems. Use when analyzing performance problems, workflow inefficiencies, project bottlenecks, or when user mentions constraints, throughput, bottlenecks, or system optimization.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Applies Cynefin framework for sense-making and decision-making across different contexts. Use when analyzing problem types, determining appropriate responses, making decisions under uncertainty, or when user mentions complexity, chaos, sense-making, problem classification, or asks which approach to use for a situation.
Operate, configure, and troubleshoot the ductile integration gateway CLI. Use this skill when the user wants to: run ductile commands, manage plugins or pipelines, configure the gateway, inspect jobs, trigger API calls, manage tokens/webhooks, validate or lock config, or understand ductile architecture. Triggers: any mention of "ductile", "config lock", "plugin list", "job inspect", "system start", pipeline DSL, or integration gateway tasks.
Applies critical thinking about models, frameworks, and representations. Use when discussing mental models, when models seem to contradict reality, when frameworks are being applied rigidly, or when user mentions abstraction, perception, assumptions, or asks about limitations of models or frameworks.
Root Cause Analysis thinking tool for technical problem-solving. Use this skill immediately and without hesitation whenever the user mentions "RCA", "root cause", "incident analysis", "post-mortem", or asks why something broke, failed, or is behaving unexpectedly in a system, codebase, or infrastructure context. Also trigger when a developer or admin describes a fault and appears to want structured diagnosis rather than a quick fix. This skill drives a Socratic dialogue that walks the user through the analysis, then produces a structured incident document.
Creates strategic Wardley Maps showing value chains and component evolution. Use when analyzing business strategy, technology decisions, competitive positioning, or when user mentions value chains, evolution, strategic mapping, competitive landscape, or asks about "where to play" or "how to win".
Create and manage a Zettelkasten-style knowledge vault using Obsidian Flavored Markdown. Use this skill whenever the user wants to capture notes, ideas, research, meeting notes, or any knowledge in a structured way — especially when they mention "vault", "zettelkasten", "atomic notes", "zettels", "knowledge base", "second brain", "evergreen notes", "note-taking", or want to link ideas together. Always use this skill when creating .md files that should live in the vault, not just standalone markdown. Strongly prefer this skill over the generic obsidian-markdown skill when the intent is knowledge management rather than one-off document creation.
| name | theory-of-constraints |
| description | Applies Theory of Constraints methodology to identify bottlenecks and optimize systems. Use when analyzing performance problems, workflow inefficiencies, project bottlenecks, or when user mentions constraints, throughput, bottlenecks, or system optimization. |
Apply constraint-first thinking to identify and address the limiting factor in any system.
When analyzing a problem using ToC, follow these steps sequentially:
Find the single most limiting factor in the system.
Key questions:
Common constraint types:
Get maximum value from the constraint before considering changes.
Exploitation strategies:
Questions to ask:
Align all other activities to support the constraint.
Subordination principles:
Key insight: Optimizing non-constraints doesn't improve overall system performance.
If the constraint still limits the system, increase its capacity.
Elevation options:
Before elevating, verify:
Once a constraint is broken, a new constraint emerges.
Important: Don't let inertia become the constraint. When the constraint moves, update all policies and procedures.
Use this workflow when analyzing a system or problem:
Analysis Checklist:
- [ ] Step 1: Map the system and identify the constraint
- [ ] Step 2: Analyze current constraint utilization
- [ ] Step 3: Propose exploitation improvements
- [ ] Step 4: Check subordination (are non-constraints aligned?)
- [ ] Step 5: Assess if elevation is needed
- [ ] Step 6: Identify what will be the next constraint
Understand the system:
Gather evidence:
Identify the constraint:
Propose improvements:
Predict outcomes:
Typical constraints:
Example analysis:
Constraint: Code reviews taking 2-3 days
Exploit: Reviewers focus on review before new coding
Subordinate: Developers write smaller PRs, include context
Elevate: Add more reviewers, automated checks
Typical constraints:
Typical constraints:
Drum-Buffer-Rope:
Throughput Accounting:
Continuous Improvement:
ToC is powerful but not always the right framework:
For these situations, consider other frameworks (design thinking, agile, lean, systems thinking).
Scenario: Development team shipping features slowly
1. Identify: Code reviews are the constraint (avg 3-day wait)
2. Exploit:
3. Subordinate:
4. Elevate (if needed):
5. Next constraint: After solving reviews, testing becomes the bottleneck. Repeat the process.
When analyzing any problem, ask:
Remember: A chain is only as strong as its weakest link. Strengthening other links doesn't help until you strengthen the weakest one.