systems-thinking

Guides systemic problem analysis through iterative questions and Causal Loop Diagrams.

13|5|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mlevison/agent-thinking-skills --skill systems-thinking-mlevison
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systems-thinking
Source: https://github.com/mlevison/agent-thinking-skills/tree/main/skills/systems-thinking
Command: npx skills add https://github.com/mlevison/agent-thinking-skills --skill systems-thinking-mlevison

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recurring problems often persist because quick fixes treat symptoms instead of the feedback loops holding the situation in place. This Skill helps you trace causes upstream, surface hidden assumptions, and understand why a problem keeps coming back before committing to a solution. ## Core Features & Use Cases - Guided Questioning: Offers one question at a time from the Questions of a Systems Thinker set, covering perspective shifts, time horizons, system structure, and assumptions. - Causal Loop Diagrams: Generates Mermaid-based CLDs with polarity labels, reinforcing/balancing loop identification, and color-coded variables when you describe 3+ interconnected factors. - Temporal Orientation: Distinguishes forward-looking planning from backward-looking diagnosis and adapts the analysis accordingly. - Use Case: Your team keeps missing deadlines despite adding process. Describe the situation, and the Skill helps you map the loop (pressure → shortcuts → rework → more pressure) and find where intervention would actually stick. ## Quick Start Ask the assistant to help you analyze why a problem keeps recurring using systems thinking, describing the situation and the factors involved.

Frequently Asked Questions about systems-thinking

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

FAQPage Schema
How do I analyze a problem that keeps coming back?▼

Describe the recurring problem and the factors involved. The Skill asks one question at a time to expand your perspective, trace the problem's history, and map connections, helping you find the feedback loops holding the situation in place rather than applying another quick fix.

How do I create a Causal Loop Diagram?▼

Identify 3-7 variables that change over time, then determine whether each pair moves in the same (+) or opposite (-) direction. The Skill generates a Mermaid diagram with color-coded variables and labels reinforcing (R) and balancing (B) loops.

When should I use systems thinking instead of root cause analysis?▼

Use systems thinking when problems recur despite fixes, when fixing one thing breaks another, or when multiple interacting factors are involved. Linear root cause analysis suits single-cause failures; systems thinking addresses circular causation and feedback loops.

What makes a good variable name for a Causal Loop Diagram?▼

Use neutral nouns that can go both up and down, such as Team Morale or Error Rate. Avoid directional names like Increasing Costs, negative phrasings like Lack of Trust, and verbs. Test each name by asking whether it works with level of or amount of.

What are the limitations of Causal Loop Diagrams?▼

CLDs show qualitative relationships but not magnitudes or exact timing, and they can become unreadable with too many variables. Keep diagrams to 3-7 variables, avoid using time itself as a variable, and treat correlation cautiously rather than assuming causation.