thinking-in-systems
Skill1 starsChanged 2 months agoMITView on GitHub
Apply Donella Meadows's systems thinking to recurring problems involving stocks, flows, feedback, delays, or conflicting incentives. Use for persistent backlogs, capacity problems, policy resistance, and unintended consequences; ordinary isolated fixes do not require a system model.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- JustYannicc/skillstheir own version, first seen Nov 1, 2026
- marcos-sponton/frameworks-as-skillstheir own version, first seen Oct 13, 2026
- chenhunghan/thinking-in-systems-skilltheir own version, first seen Apr 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- JustYannicc/skills★ 3same name
- marcos-sponton/frameworks-as-skills★ 1same name
- chenhunghan/thinking-in-systems-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- algorithms-to-live-bySkill
- analectsSkill
- antifragileSkill
- art-of-doing-scienceSkill
- art-of-warSkill
- beginning-of-infinitySkill
- bhagavad-gitaSkill
- book-of-whySkill
- brothers-karamazovSkill
- capital-volume-oneSkill
- design-of-everyday-thingsSkill
- development-as-freedomSkill
- dhammapadaSkill
- don-quixoteSkill
- dream-of-red-chamberSkill
- euclid-elementsSkill
- feynman-lecturesSkill
- good-strategy-bad-strategySkill
- governing-the-commonsSkill
- how-to-solve-itSkill
- human-understandingSkill
- make-it-stickSkill
- mans-search-for-meaningSkill
- meditationsSkill
- muqaddimahSkill
- nicomachean-ethicsSkill
- on-libertySkill
- origin-of-speciesSkill
- republicSkill
- scientific-revolutionsSkill
- second-sexSkill
- seeing-like-a-stateSkill
- selfish-geneSkill
- sicpSkill
- superforecastingSkill
- tao-te-chingSkill
- the-mom-testSkill
- thinking-fast-and-slowSkill
- wealth-of-nationsSkill
The file
Files
Thinking in Systems:找到反复发生的原因
把一个持续出现的问题转成可检验的系统假说和一项小范围干预。基于 Meadows 的公开作者文章及出版社说明;应用步骤是本项目的原创改编,不声称覆盖全书。
从现象进入模型
先从现有材料取得:问题持续多久、随时间怎样变化、希望改变的量、谁能改变什么,以及最近采取过什么措施。不要把单个坏结果直接当作系统规律。资料不足时列出暂定边界,继续建立小模型,并说明最值得补的一项观察。
- 区分积累量和变化速率。 选一个核心存量,如待处理工单,标单位“件”;分别列流入和流出,标单位“件/天”。写出
期末存量 = 期初存量 + 期间流入 - 期间流出。不能测量的信任、疲劳等只作定性变量,不虚构数量。 - 画出反馈,而非只画线性原因链。 标出变量影响方向和证据。强化回路会放大变化,平衡回路会调节差距;两者不等于好和坏。未知箭头标为假说,不能靠一张图证明因果。
- 标明延迟和系统边界。 区分信息延迟、决策延迟和实际产能变化延迟。检查短期改善是否把工作转移到别处,或用返工、疲劳、客户流失换取局部指标。对不可缩短的延迟,考虑降低调整幅度或速度。
- 比较不同层次的干预。 至少在当前最相关的两层比较:参数/缓冲容量、反馈与信息、规则与目标。不要机械列出全部十二类,也不要声称改变“心智模式”必然最有效。参数跨越关键阈值或改变反馈强度时也可能重要;例如在无返工的简化队列里,完成率由低于到达率变为高于到达率,会把积压由增长变为下降。先用具体机制说明例外,再选证据足、能实施、后果可观察的方案。
- 设计一个能够推翻模型的小实验。 写出干预、预期机制、观察窗口及停止或回退条件;至少有一个目标指标和一个副作用指标。观察窗口应容纳已知延迟。说明什么结果将使你放弃当前解释。
交付与判断
先给最值得采取的动作,再给简洁模型、证据/假说区别、干预比较和验证安排。表格或小图只在确实减轻理解负担时使用。用户只要求分析时交付建议,不替其更改组织规则或执行外部操作。
遇到数学上的存量计算可以精确求解;真实系统的未知关系只能给条件预测。库存减少并不自动表示服务改善,短期吞吐增长也不代表长期产能提升。
作者明确把杠杆点清单视为暂定、有例外的思考邀请;本 Skill 不能用它为任何特定公共政策作权威背书。需要确认观点归属、年份或引用时读 来源说明;需要具体建模示范时读 工单积压案例。书目见 book.json,行为评估场景见 cases.json。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

