Think through consequences of consequences
Analyze decisions by tracing their consequences through multiple levels. Use this when evaluating architectural choices, refactoring strategies, or process changes to avoid unintended downstream effects and identify compounding benefits.
/plugin marketplace add shishiv/shishiv-resources/plugin install shiv-resources@shishiv-resourcesaction or leave blank for current contextconsider/Ask: "And then what?" First-order thinking stops at immediate effects. Second-order thinking follows the chain. </objective>
<process> 1. State the action or decision 2. Identify first-order effects (immediate, obvious consequences) 3. For each first-order effect, ask "And then what happens?" 4. Continue to third-order if significant 5. Identify delayed consequences that change the calculus 6. Assess whether the action is still worth it after full chain analysis </process><output_format> Action: [what's being considered]
First-Order Effects: (Immediate)
Second-Order Effects: (And then what?)
Third-Order Effects: (And then?)
Delayed Consequences: [Effects that aren't obvious initially but matter long-term]
Revised Assessment: After tracing the chain, this action [is/isn't] worth it because... </output_format>
<success_criteria>