Sequential Thinking

When to Use

• Complex debugging
• Architecture decisions
• Security analysis
• Performance investigation
• Any problem with multiple possible causes
• When decisions need documentation

When NOT to Use

• Simple straightforward tasks where the answer is obvious and well-known
• Mechanical code changes like renames, formatting, or boilerplate generation
• When the MCP sequential-thinking server is unavailable and structured tool support is needed