thinking-in-systems-state-machine-skill

System dynamics mapping identifies interactions, feedback loops, and delays before action to prevent cascading failures and downstream effects across subsystems. You need it for tasks with multi-step consequences requiring upfront boundary mapping.

Document feedback loops and unknowns by creating mandatory diagnostic artifacts like system-feedback-map.md before executing bounded interventions. This maps the blast radius and identifies unknowns to guide safe, governed execution across subsystems.

Apply a state-machine workflow by enforcing creation of diagnostic artifacts first, then governing execution through bounded, safe interventions. This protocol ensures system boundaries and feedback loops are mapped before any action is taken.

Upfront system mapping should be avoided for simple tasks lacking interactions, feedback loops, delays, or multi-step downstream consequences. It is only necessary for system-dynamics problems with cascading effects across subsystems.

The best way to prevent cascading failures is identifying system-dynamics problems upfront and mapping boundaries and feedback loops before action. This structured protocol enforces diagnostic artifacts and documents blast radius to ensure safe interventions.