SystemsThinking

Analyzes complex systems using causal loop diagrams, archetypes, and Meadows' leverage points.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/ruban-s/DevOS --skill systemsthinking-ruban-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SystemsThinking
Source: https://github.com/ruban-s/DevOS/tree/main/skills/SystemsThinking
Command: npx skills add https://github.com/ruban-s/DevOS --skill systemsthinking-ruban-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recurring bugs, stalled growth, and fixes that backfire persist because event-level patches never reach the structure generating the behavior. This Skill walks analysis from visible symptoms down to feedback loops, archetypes, and mental models so interventions target the actual cause. ## Core Features & Use Cases - Iceberg Analysis: Descend from events through patterns and structures to the mental models generating them. - Causal Loop Diagrams: Map reinforcing and balancing feedback loops with polarity and delays to preview second-order effects before shipping a change. - Archetype Matching: Recognize the 10 canonical systems archetypes (Fixes That Fail, Tragedy of the Commons, Limits to Growth, and more) and apply their documented interventions. - Leverage Point Selection: Rank candidate interventions against Meadows' 12 leverage points, from weak parameters to paradigm shifts. - Use Case: When adding engineers past team size 12 slows delivery, the FindArchetype workflow matches Limits to Growth and recommends attacking coordination cost rather than slowing hiring. ## Quick Start Ask the assistant to use the SystemsThinking skill to explain why the same class of production incident keeps recurring despite repeated fixes.

Frequently Asked Questions about SystemsThinking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a recurring problem with systems thinking?▼

Use the Iceberg workflow to descend from the visible event through recurring patterns to the structure and mental models generating them. Then build a causal loop diagram to confirm the feedback loops driving the behavior before choosing an intervention.

What is a causal loop diagram and how do I build one?▼

A causal loop diagram connects 5-15 variables with arrows labeled by polarity, where plus means same-direction change and minus means opposite. Loops with an even count of negative arrows are reinforcing and amplify change; odd counts are balancing and seek a goal.

What are the most common systems archetypes to recognize?▼

The ten canonical archetypes include Fixes That Fail, Shifting the Burden, Limits to Growth, Tragedy of the Commons, and Drifting Goals. Each has a documented loop structure and canonical intervention, so matching the pattern unlocks a known fix.

When should I not use systems thinking analysis?▼

Skip it for genuinely complicated problems with knowable cause-effect chains, acute crises requiring immediate firefighting, and simple domains where best practices already exist. It also fails when stakeholders cannot agree on system boundaries.

What are Meadows' leverage points and which ones matter most?▼

Meadows' 12 leverage points rank intervention targets from weakest (parameters, buffers) to strongest (system goals, paradigms, transcending paradigms). Effective leverage combines the level's strength with feasibility, so bundle a tactical low-level fix with a structural high-level change.