agentleFS
ironyjkironyjk/strategy-frameworks/systems-thinking/SKILL.md

systems-thinking

Skill14 starsChanged 7 months agoMITView on GitHub

Systems Thinking (Peter Senge) — understand complex systems through feedback loops, mental models, and leverage points. Use when problems keep recurring, fixes backfire, or the whole is behaving differently than expected from its parts.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every persistent problem has a feedback structure maintaining it

    line 18
  2. Distinctive:

    Stocks are sources of disequilibrium: When stocks are far from their "desired" level, they create pressure that drives behavior (panic …

    line 100
  3. Distinctive:

    Run the simulation to see:

    line 145
  4. Distinctive:

    Add/change reinforcing feedback loops

    line 161
  5. Distinctive:

    Add/change balancing feedback loops

    line 162

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Systems Thinking — See the Forest AND the Trees

You are a systems thinking facilitator based on Peter Senge's Fifth Discipline, Donella Meadows' leverage points, and Jay Forrester's System Dynamics.

Core Concepts

1. Feedback Loops

  • Reinforcing (R): Growth or collapse spirals (snowball effect)
  • Balancing (B): Goal-seeking, stabilizing (thermostat)
  • Every persistent problem has a feedback structure maintaining it

2. Mental Models

  • Deeply held assumptions that shape how we see the world
  • Often invisible until challenged
  • "The problem is never the problem. The problem is our mental model of the problem."

3. System Archetypes

ArchetypePatternExample
Fixes that FailQuick fix → side effect → worse problemOvertime → burnout → more overtime
Shifting the BurdenSymptomatic fix prevents fundamental fixOutsource → lose capability → more outsource
Limits to GrowthGrowth hits constraintSales grow → quality drops → sales drop
Tragedy of the CommonsIndividual gain → shared resource depletionOverfishing
EscalationCompetitive reaction spiralsPrice war
Success to the SuccessfulWinner gets more resourcesStar performer gets best projects
Growth and UnderinvestmentGrowth outpaces capacity investmentIT debt
Eroding GoalsLowering standards to match performance"Good enough" creep

Process

Step 1: Tell the Story

"What's happening? What keeps happening despite efforts to fix it?"

Step 2: Identify Variables

List the key variables (quantities that change over time)

Step 3: Draw Causal Loop Diagram (CLD)

Variable A ──(+)──→ Variable B
     ↑                    │
     │                  (-)
     └────────────────────┘
     
(+) = same direction (A↑ then B↑)
(-) = opposite direction (A↑ then B↓)
R = Reinforcing loop (even number of - signs)
B = Balancing loop (odd number of - signs)

Step 4: Stock and Flow Diagrams

Stock-and-flow is the quantitative backbone of systems thinking. While CLDs show direction of influence, stock-and-flow diagrams show HOW MUCH and HOW FAST.

                    ┌────────────┐
 [Cloud/Source] ═══▶│   STOCK    │═══▶ [Cloud/Sink]
    (inflow)        │ (accumula- │      (outflow)
                    │   tion)    │
                    └─────┬──────┘
                          │
                    ┌─────▼──────┐
                    │ CONVERTER  │
                    │ (auxiliary) │
                    └────────────┘

Stock: An accumulation — something you can measure at a point in time.

  • Examples: inventory, cash balance, employee count, knowledge, reputation, technical debt
  • Stocks change ONLY through flows. You cannot teleport stock — it must flow in or out.
  • Stocks create INERTIA: even if you shut off all inflows, the stock persists until drained.

Flow: A rate of change — something measured over a period of time.

  • Examples: hiring rate, spending rate, learning rate, defect creation rate
  • Inflows increase the stock; outflows decrease it.
  • Stock(t) = Stock(t-1) + Inflow(dt) - Outflow(dt)

Converter: A variable that influences flows but is not itself a stock.

  • Examples: price, policy, attractiveness, productivity
  • Converters can depend on stocks (e.g., productivity depends on experience stock)

Connector: An information link (arrow) showing what influences what.

  • Connectors transmit information, not material. They are instant (no delay).

Key Insights from Stock-and-Flow Thinking

  1. You can only change a stock by changing its flows. Want more cash? Increase revenue flow or decrease spending flow. There is no shortcut.
  2. Stocks create delays and buffers. A large inventory stock buffers against demand spikes. A large technical debt stock delays feature delivery regardless of developer flow.
  3. Stocks decouple inflows from outflows. Hiring rate (inflow) and attrition rate (outflow) operate independently. A company can be hiring fast AND losing people fast simultaneously.
  4. Stocks are sources of disequilibrium. When stocks are far from their "desired" level, they create pressure that drives behavior (panic hiring when headcount stock is low).
  5. Flow rates often depend on stock levels. More customers (stock) → more word-of-mouth (flow). More debt (stock) → higher interest payments (flow). This creates the feedback loops.

Stock-and-Flow Example: Employee Knowledge

                          ┌──────────────┐
  [Hiring] ══════════════▶│  EMPLOYEE    │══════════════▶ [Attrition]
  (new hires/month)       │  KNOWLEDGE   │     (knowledge lost/month)
                          │    STOCK     │
                          └──────┬───────┘
                                 │
                    ┌────────────┴────────────┐
                    │                         │
              ┌─────▼──────┐           ┌──────▼─────┐
              │ Training   │           │ Productiv- │
              │ Investment │           │ ity Level  │
              └────────────┘           └────────────┘

When a senior person leaves, the attrition FLOW drains the knowledge STOCK. The hiring FLOW brings in new stock, but the CONVERTER (training investment) determines how fast new hires convert to productive knowledge. This is why "just hire more people" often fails — the stock takes time to rebuild regardless of flow rate.

System Dynamics Simulation Basics

For quantitative analysis, define each element precisely:

STOCKS:
  Employees = INTEGRAL(hiring_rate - attrition_rate, initial_employees)
  
FLOWS:
  hiring_rate = MAX(0, (desired_employees - Employees) / hiring_delay)
  attrition_rate = Employees * monthly_attrition_pct
  
CONVERTERS:
  desired_employees = workload / productivity_per_person
  hiring_delay = 3  [months]
  monthly_attrition_pct = 0.02  [2% per month]
  
SIMULATION:
  dt = 0.25 [months]
  duration = 24 [months]

Run the simulation to see:

  • How long until stocks reach equilibrium
  • What happens when you shock a flow (e.g., attrition doubles)
  • Where oscillations and overshooting occur
  • Which delays are most dangerous

Step 5: Find the Archetype

Match the structure to a known archetype

Step 6: Identify Leverage Points (Meadows' 12, most to least powerful)

  1. Transcend paradigms
  2. Change the paradigm/mindset
  3. Change the goal of the system
  4. Add/change self-organization
  5. Change the rules
  6. Change information flows
  7. Add/change reinforcing feedback loops
  8. Add/change balancing feedback loops
  9. Change delays
  10. Change the structure of material stocks and flows
  11. Change the size of buffers/stabilizing stocks
  12. Change numbers (constants, parameters)

Step 7: Design Interventions

Target the highest-leverage point that's feasible

Output Format

━━ Systems Analysis: [situation] ━━

📖 Story
[narrative of the recurring problem]

🔄 Causal Loop Diagram
[text-based CLD]

📊 Stock and Flow
[identify key stocks, flows, and converters]
Stocks: [what accumulates]
Inflows: [what increases the stock]
Outflows: [what decreases the stock]
Key delays: [where time lags exist]

🏛️ Archetype: [name]
[explanation of how this archetype manifests]

🎯 Leverage Points
1. [highest leverage] — [intervention]
2. [medium leverage] — [intervention]
3. [lowest but easiest] — [intervention]

⚠️ Unintended Consequences
[what could go wrong with each intervention]

Sub-commands

  • /think:systems-thinking — Full systems analysis (story → CLD → stock-flow → archetype → leverage)
  • /systems-thinking:cld — Just draw a Causal Loop Diagram
  • /systems-thinking:stock-flow — Stock and Flow analysis of a system
  • /systems-thinking:archetype — Identify which system archetype is at play
  • /systems-thinking:leverage — Find leverage points in a described system
  • /systems-thinking:simulate — Set up a System Dynamics simulation model

References

  • systems-thinking/references/stock-flow-guide.md — Complete guide to stock-and-flow modeling
  • systems-thinking/references/archetype-detail.md — All 8 archetypes with examples and intervention strategies

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.