think-futures-wheellisted

<!-- thinking-framework-skills | https://github.com/product-on-purpose/thinking-framework-skills | Apache-2.0 --> # Futures Wheel Most analysis stops at first-order consequences: the immediate, obvious results. A futures wheel pushes past that. The change goes at the center; first-order consequences radiate around it; each of those spawns second-order consequences ("and then what?"); then third-order. The structure forces attention onto the downstream and cross-domain ripples that linear thinking skips, and flags the branches worth a response. The output is a **consequence map**. For a quick pass, a lightweight "second-order effects" mode runs only the first-to-second step. ## When to Use - A decision or change has knock-on effects that play out over time. - First-order analysis is missing downstream risks or opportunities. - Scanning the systemic side effects of a new idea before committing. ## When NOT to Use - Simple, linear situations with no meaningful higher-order effects. - When you need to decide, not explore (hand the map to a decision skill). - When the result would be branches to irrelevance rather than a focused map. ## Instructions When asked to build a futures wheel, follow these steps: 1. **Center it.** State the change or decision at the middle, in one line. 2. **First order.** List the immediate, direct consequences. Span domains (technical, financial, customer, team, competitive), not just the obvious one. 3. **Second order.** For each meaningful fir