sequential-thinking

Structured step-by-step problem solving is a technique that decomposes complex problems into tracked sequences with explicit revision and branching. You need it when debugging, designing architecture, or testing hypotheses where assumptions and uncertainties must be monitored.

To debug using sequential reasoning, you decompose the issue into step-by-step thoughts, explicitly track assumptions, and use branching to compare alternative hypotheses. You can revise previous thoughts as new information emerges to converge on a robust solution.

Yes, you can compare alternative approaches during complex problem decomposition by using the branching feature. Branching allows you to explore different paths simultaneously, test hypotheses, and verify which sequence converges on the most robust solution.

No, you do not need external tooling to track thought history or validate hypotheses. The process relies entirely on included scripts for deterministic validation, thought history tracking, and formatted thought presentation without any external dependencies.

A limitation of using adaptive planning for architecture decisions is the overhead of explicitly tracking every assumption, uncertainty, and realization. This structured approach may be excessive for simple problems that do not require complex decomposition or branching.

The best way to revise assumptions during stepwise analysis is to leverage the explicit revision capability. This allows you to modify previous thoughts, update tracked assumptions, and adapt your plan as new realizations emerge throughout the problem-solving sequence.