systems-thinking

Analyze recurring problems by mapping root causes and feedback loops.

7|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mlevison/systems-thinking --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/systems-thinking/tree/main
Command: npx skills add https://github.com/mlevison/systems-thinking --skill systems-thinking-mlevison

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systems Thinking helps you stop treating recurring issues like isolated events and instead understand the upstream causes, feedback loops, and assumptions that keep them happening.

Core Features & Use Cases

  • Guided, one-question-at-a-time analysis: Surfaces the right perspective shifts (zooming out/in, time-tracing, and mapping connections) without prescribing a fixed solution path.
  • Causal Loop Diagram (CLD) creation: Turns described cause-and-effect relationships into a feedback-loop map to reveal reinforcing and balancing dynamics.
  • Use cases: Great for recurring operational problems, seemingly conflicting outcomes, ripple-effect planning, and diagnosing why “reorgs” or interventions don’t change results.

Quick Start

Ask the skill to analyze your situation using Systems Thinking and then follow its next question to map the system’s connections and feedback loops.

Frequently Asked Questions about systems-thinking

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

FAQPage Schema
How do I find the root cause of a recurring operational problem?

Root cause analysis of recurring operational problems is done by mapping upstream causes and feedback loops rather than treating isolated events. This approach guides you iteratively to reveal the reinforcing and balancing dynamics keeping the issue active.

What is a causal loop diagram and when do I need one?

A causal loop diagram turns described cause-and-effect relationships into a feedback-loop map to reveal reinforcing and balancing dynamics. You need one when planning ripple effects or diagnosing why interventions and reorganizations fail to change results.

How do I analyze complex problem solving scenarios step by step?

Complex problem solving is handled iteratively by asking one question at a time to map system connections. This shifts perspective by zooming out, time-tracing interactions, and building structured causal narratives without prescribing a fixed solution path.

Why does my organizational change initiative fail to produce lasting results?

Organizational change often fails when recurring issues are treated as isolated events. By applying systems thinking to map feedback loops and underlying assumptions, you can diagnose the systemic structures preventing your interventions from working.

Can I use root cause analysis for planning ripple effects before implementation?

Root cause analysis applies to planning ripple effects by mapping the cause-and-effect relationships of a proposed intervention. It helps you anticipate conflicting outcomes and understand how changes will propagate through the system.

What are the limitations of systems thinking for multi-factor troubleshooting?

Systems thinking for multi-factor troubleshooting guides you to map relationships rather than prescribing fixed solutions. It is limited when you need definitive answers, as it focuses on surfacing assumptions and perspectives without providing a direct fix.