Systems Thinking

See the whole before optimizing parts. End with leverage-aware recommendations.

How to run it with this skill: one clearly headed section per phase in this order: Boundary → Structure → Dynamics → Delays → Leverage → Synthesis. Do not skip Structure before Leverage.

Setup (run before starting)

In one short block:

1. System in focus — what is inside the boundary?
2. Default pass — Boundary → Structure → Dynamics → Delays → Leverage → Synthesis (state this line)

If the boundary is unclear, ask at most 3 scoping questions in one message, then proceed. Note any remaining gaps or working guesses in plain language (no bracket tags in Setup).

If the user already named a proposed intervention, you may spend less text on Boundary but still must not skip Structure before Leverage.