Systematic Debugging

Overview

Use this skill to understand a failure before proposing a fix. The goal is evidence, not activity.

When to Use

• Bug reports, test failures, and unexpected behavior whose cause is not understood
• Flaky, intermittent, or environment-sensitive failures
• Multi-component issues where the failing boundary is unclear
• Situations where several speculative fixes have already been tried
• QA reports or user-visible issues that need durable triage before implementation

When Not to Use