sequential-thinking

Structured reasoning for architecture decisions uses a seven-step workflow to frame the problem context, decompose dependencies, and validate outcomes. You define success criteria first, then generate hypotheses before planning concrete implementation steps.

Breaking down complex debugging problems involves decomposing the issue into actionable sub-problems and dependencies. You frame the exact error context, hypothesize potential root causes, analyze the results, and decide on a validated fix.

Step-by-step problem solving applies directly to requirements analysis by framing constraints and success criteria upfront. You decompose broad requirements into manageable components, hypothesize user needs, and validate the planned features.

Structured thinking helps evaluate technical hypotheses by providing a repeatable process to generate explanations and analyze results systematically. You document findings after testing each idea to ensure well-reasoned conclusions.

Validating decisions in software engineering requires outlining concrete steps and verifying the results against initial success criteria. The process ensures you choose a path only after analyzing all decomposed dependencies and documented hypotheses.