ultrathink

To plan software architecture before writing code, outline a high-level architecture plan detailing components, interfaces, data flow, and risk mitigations. This architecture-first approach maps dependencies and edge cases to ensure robust design decisions.

Structured deep thinking for complex problem solving is a disciplined approach enforcing step-by-step reasoning, hypothesis generation, and rigorous critique. It prevents shallow problem-solving by ensuring detail-oriented reasoning for robust software design.

To map dependencies and data flows when redesigning a module, apply a structured thinking framework to guide your analysis. This enforces detailed attention to edge cases and data flows before writing code, yielding well-justified conclusions.

Yes, structured thinking helps with software documentation by producing well-justified conclusions with trade-offs for stakeholders. It enforces documentation practices that capture rigorous reasoning and repeatable design decisions.

You should use an architecture-first planning approach for debugging when attention to detail matters in complex tasks. It enforces a disciplined, detail-oriented thinking approach to prevent shallow problem-solving and ensure robust design decisions.