Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Analiza

systems-thinking

/systems-thinking

Analizuje problemy z wieloma aktorami, pętlami sprzężenia zwrotnego, opóźnieniami i bodźcami: diagramy pętli przyczynowych, mapowanie systemu i wskazywanie punktów dźwigni.

Licencja
Apache-2.0
Ostatnia zmiana repozytorium
10.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 10.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Analizuje problemy z wieloma aktorami, pętlami sprzężenia zwrotnego, opóźnieniami i bodźcami: diagramy pętli przyczynowych, mapowanie systemu i wskazywanie punktów dźwigni.

Oryginalny opis (EN)

Use when a problem involves interacting actors, feedback loops, delays, incentives, constraints, unintended consequences, or repeated patterns over time. Use when applying systems thinking, causal loop analysis, system mapping, leverage point identification, or dynamic complexity diagnosis.

Jak działa

  1. Method Notes
  2. Required Inputs
  3. When Not To Use
  4. Adjacent Methods
  5. Step-by-Step Execution
  6. Output Template
  7. Quality Gate
Sekcje z nagłówków SKILL.md, w oryginale · 101 linii, 1 019 słów
Podgląd SKILL.md
---
name: systems-thinking
description: Use when a problem involves interacting actors, feedback loops, delays, incentives, constraints, unintended consequences, or repeated patterns over time. Use when applying systems thinking, causal loop analysis, system mapping, leverage point identification, or dynamic complexity diagnosis.
license: Apache-2.0
---

# Systems Thinking

Use this skill to understand how parts of a system interact and why behavior persists over time.

## Method Notes

- Systems thinking focuses on relationships, feedback loops, delays, incentives, and patterns.
- It is useful when direct cause-and-effect explanations are too shallow.
- L0 diagnoses dynamic mechanisms and identifies evidence to validate; L1 also evaluates leverage points and stress-tests a proposed intervention. Neither level needs a complicated map for its own sake.
- Keep the system boundary explicit so the analysis stays usable.

## Required Inputs

Collect or infer these inputs before execution:

- system or problem boundary
- actors, components, processes, or variables
- repeated pattern or outcome
- incentives, constraints, and feedback signals
- time horizon and behavior-over-time pattern
- time delays or unintended consequences
- evidence for relationship direction, loop logic, and expected trend

If an input is missing, mark it as `missing`, state the assumption used, and add a validation action.

## When Not To Use

Do not use when the issue is a one-off decision with stable criteria. Use `decision-matrix`, `deductive-reasoning`, or `risk-matrix` instead.

## Adjacent Methods

- `five-whys-root-cause`: one linear cause chain.
- `fishbone-diagram`: several operational cause categories.
- `constraint-analysis`: one binding bottleneck.

## Step-by-Step Execution

| Step | Required input | How to execute | Output |
|---|---|---|---|
| Select level and boundary | Decision need, scope, time horizon, available evidence. | Choose L0 for a qualitative dynamic map or L1 when a proposed intervention must be stress-tested. State what is inside, outside, and not modeled. | Level statement and system boundary. |
| Describe behavior over time | Outcome history, trend, recurring episodes, baseline. | Describe the pattern before explaining it: growth, decline, oscillation, plateau, overshoot, or repeated return. Mark missing time-series evidence. | Behavior-over-time pattern. |
| Identify key variables | Actors, resources, decisions, behaviors, metrics, constraints. | Keep only variables that can materially change the outcome within the chosen horizon. Mark owner and evidence strength. | Decision-relevant variable list. |
| Map directional relationships | Variables, observations, causal evidence. | For each link, state whether the source increases or decreases the target, assign positive, negative, or unknown polarity, and mark delay and evidence. | Signed relationship map. |
| Close feedback loops | Signed relationships. | Trace closed paths. Label reinforcing loops that amplify change and balancing loops that counter it. Do not call an open chain a loop. | Named R/B loops and dominant conditions. |
| Add delays, incentives, and constraints | Process timing, rules, rewards, decision rights. | Show where response is delayed, which incentives create behavior, and which constraints limit adjustment. | Dynamic mechanism diagnosis. |
| Identify leverage points | Loops, constraints, control rights, intervention options. | For L1, find changes that alter information, incentives, rules, capacity, delay, or decision rights; rate controllability and evidence. For L0, record diagnostic mechanisms and validation needs without requiring ranked leverage points or intervention selection. | L0 diagnostic mechanisms or L1 ranked leverage points. |
| Stress-test intervention | Proposed action, loops, delay, affected actors. | For L1, predict direction over time, lag, compensating response, side effects, and problem displacement; define a lower-regret version. For L0, mark this step N/A because the selected scope is diagnosis only. | L1 intervention stress test. |
| Define learning loop | Expected trend, leading indicators, review cadence. | Set signals, thresholds, owner, review date, and the assumption that must be revised if the pattern differs. | Monitoring and model-revision plan. |

## Output Template

```markdown
### 1. Level, Boundary, And Time
- Analysis level: L0 qualitative dynamic map / L1 decision stress test
- Problem / system:
- In scope:
- Out of scope:
- Time horizon:
- Behavior-over-time pattern:

### 2. Variables And Relationships
| From variable | Direction | To variable | Polarity (+/-/unknown) | Delay | Evidence / assumption |
|---|---|---|---|---|---|
|  | increases / decreases |  |  |  |  |

### 3. Feedback Loops
| Loop | Type | Mechanism | Dominant when | Evidence strength |
|---|---|---|---|---|
|  | reinforcing / balancing |  |  |  |

### 4. Incentives, Constraints, And Leverage
L0: describe incentives, constraints, and diagnostic mechanisms; leverage point and control owner may be N/A with a reason. L1: identify leverage points and control owners.
| Actor / rule | Incentive or constraint | Behavior created | Leverage point | Control owner |
|---|---|---|---|---|
|  |  |  |  |  |

### 5. Intervention Stress Test
L0: mark this section N/A because the selected scope is diagnosis only; do not select an intervention to fill the table. L1: complete the table for at least one proposed intervention.
| Intervention | Expected direction over time | Delay | Side effect / displacement | Low-regret adjustment |
|---|---|---|---|---|
|  |  |  |  |  |

### 6. Leading Signals And Model Revision
| Signal | Expected trend | Review date | Continue / adjust / stop threshold | Model assumption revised if |
|---|---|---|---|---|
|  |  |  |  |  |
```

## Quality Gate

- State whether the output is L0 or L1; never imply L2 simulation, calibrated forecasting, or quantitative stock-and-flow modeling.
- Define the system boundary, excluded scope, time horizon, and behavior-over-time pattern.
- Give each material relationship a direction and polarity; mark unknown polarity rather than inventing it.
- Include at least one reinforcing or balancing loop only when the loop closes; a long cause list is not a system map.
- Mark delays, incentives, constraints, evidence strength, and assumptions.
- For L0: do not require intervention selection or stress testing. Provide an evidence-backed or explicitly hypothetical dynamic diagnosis, the unresolved relationships, and the next evidence-validation action with an owner and review date; explain why the intervention section is N/A.
- For L1: stress-test at least one intervention for side effects, problem displacement, and delayed response; define a lower-regret adjustment. An L1 output cannot claim completion by marking the intervention test N/A.
- Define leading signals, expected trend, decision threshold, and when the model should be revised.
- Use a simpler root-cause, constraint, or decision method when dynamic complexity is absent.

Wersje

RepozytoriumWynikLicencja
Ta strona · fzfclee/consulting-skills100Apache-2.0
TerminalSkills/skills100Apache-2.0
andreibesleaga/gabbe100CC-BY-4.0
ysskrishna/ai-agent-skills100MIT
fatihguner/foreman100MIT
viktorbezdek/skillstack100MIT
carlheath/ogmios100MIT
mlevison/agent-thinking-skills90CC-BY-SA-4.0

Migawka bazy z 28.10.2026 · wersja paczki fa412ab715c5 (skrót SHA-256 całej paczki)

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100meta-systems-thinking
    Stosuje myślenie systemowe (diagramy pętli przyczynowych, modele zasobów i przepływów, archetypy, punkty dźwigni) do problemów organizacyjnych i społecznych z pętlami sprzężenia i opóźnieniami.
  • 95SystemsThinking
    Prowadzi strukturalną analizę złożonych systemów: model góry lodowej, diagramy pętli przyczynowych, dopasowanie archetypów, punkty dźwigni Meadows i mapy pojęć, przy założeniu, że zachowanie wynika ze struktury.
  • 100feedback-loop-positive-vs-negative
    Pomaga projektować architekturę systemu i mechaniki produktu z pętlami sprzężenia zwrotnego, takimi jak rekomendacje, grywalizacja i pętle wzrostu, wzmacniającymi lub stabilizującymi kolejne działania użytkowników.
  • 90lamina-systems
    Rozumuje o przyczynowych systemach produktowych i zmianie w czasie: zapasy, przepływy, opóźnienia, sprzężenia zwrotne, powtarzalne pułapki i interwencje o wysokiej dźwigni.
  • 100second-order-thinking
    Analizuje decyzje i zmiany poza ich natychmiastowym skutkiem: łańcuchy konsekwencji, reakcje interesariuszy, pętle sprzężenia zwrotnego, efekty drugiego i trzeciego rzędu oraz zabezpieczenia.
  • 90s4h-systems
    Kieruje do właściwego skilla myślenia systemowego, gdy trzeba zrozumieć pętle sprzężeń zwrotnych, miejsca interwencji, niespodziewane zachowania i dźwignie zmiany.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.