Systems Thinking

Use this skill when a local change may alter agent behavior, tool safety, documentation discoverability, operational load, or downstream workflows.

1. Define the system boundary, purpose, owners, users, and external dependencies.
2. Map inputs, outputs, stocks, flows, constraints, and state transitions.
3. Trace direct and indirect dependencies, feedback loops, delays, bottlenecks, and incentives.
4. Look for second-order effects: what the change makes easier, harder, more likely, or invisible.
5. Prefer interventions at high-leverage points: information quality, interfaces, defaults, feedback, and constraints before adding complexity.
6. Define leading indicators, guardrails, rollback conditions, and a verification plan.

Output a small causal map or table plus the proposed intervention, expected downstream effects, risks, and measurements. Treat local optimization as suspect when it worsens system-level outcomes.