sequential-thinking

Structured reasoning helps when debugging involves multiple layers—like performance bottlenecks across microservices or circular dependencies. It documents assumptions and alternatives systematically, ensuring you don't miss root causes in intricate, interconnected systems.

Problems involving architectural decisions, multi-service interactions, or timing-sensitive bugs benefit most. The Skill assesses context automatically and produces a reasoning trail only when complexity justifies it, avoiding unnecessary overhead on straightforward tasks.

A reasoning trail documents your assumptions, explores branching alternatives, traces interdependencies, and justifies decisions. This transparency makes debugging faster and helps you understand why certain paths were rejected, especially valuable for high-stakes architectural choices.

Yes. This is an ideal use case. The Skill systematically breaks down multi-service performance problems, explores potential causes across layers, and documents the reasoning so you can pinpoint bottlenecks efficiently without guessing.

For everyday tasks, overhead outweighs benefit. The Skill applies usage rules to skip activation on simple problems. For architectural decisions or intricate debugging, it activates to provide documented reasoning and ensures no critical tradeoff is overlooked.