ck:sequential-thinking

Step-by-step analysis decomposes complex debugging problems into a sequence of discrete, verifiable thoughts. You create numbered thoughts, mark revisions, and assess downstream impact to reduce errors from leaps of logic and make hypothesis verification auditable.

Sequential thinking is a structured methodology for decomposing ambiguous, multi-step problems into discrete, revisable thoughts. Use it for architecture decisions, adaptive planning, and hypothesis testing where progressive refinement and explicit branching are needed to reach a decision.

Yes, branching and hypothesis testing support allows you to explore alternative approaches in parallel. You can compare outcomes across branches and converge on a decision with explicit rationale rather than committing to a single linear path.

Thought history is persisted locally using CLI utilities that validate thought structure and format outputs for display. This local persistence ensures workflows remain deterministic and auditable without requiring external network access.

No external network access or dependencies are required. The skill operates entirely offline using local scripts and references to validate thought sequences, format outputs, and persist history locally.

Mark revisions explicitly and record why a revision occurred, then assess downstream impact on subsequent thoughts. This approach maintains full reasoning context by preserving the original thought history while tracking progressive refinement.