sequential-thinking

Break down a hard software problem using step-by-step reasoning to decompose it into explicit, numbered thoughts. This approach forces systematic analysis, surfaces hidden assumptions, and verifies hypotheses before you commit to a final solution.

The best way to plan architecture and analyze trade-offs is to use structured sequential reasoning to explore alternatives. You can branch the thought chain to compare approaches, verify logic against edge cases, and confirm correctness before implementation.

Yes, you can revise earlier steps mid-chain when debugging non-obvious issues. If new information changes your analysis, the reasoning chain allows you to update previous thoughts, generate new hypotheses, and verify them systematically.

You need structured reasoning for algorithm design when facing complex, multi-step problems that require correctness verification. It helps you systematically reason through edge cases, validate logic, and explore branching alternatives before finalizing the algorithm.

Sequential reasoning works for comparing alternative approaches by branching the thought chain into parallel paths. This allows you to systematically explore different architectural trade-offs or algorithmic solutions, evaluate their merits, and verify the best path forward.