systematic_debugging

Enforce root-cause investigation before fixing software bugs.

Updated Aug 23, 2026

Search Tags:#defense-in-depth #root-cause #phase-based #systematic-debugging #bug-triage

Ready to run

npx skills add https://github.com/FeatherHunter/StudyNotes --skill systematic-debugging-featherhunter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic_debugging
Source: https://github.com/FeatherHunter/StudyNotes/tree/main/.opencode/skills/superpowers/skills/systematic-debugging
Command: npx skills add https://github.com/FeatherHunter/StudyNotes --skill systematic-debugging-featherhunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable approach to debugging that prevents symptom-focused fixes and ensures root-cause investigation before proposing changes.

Core Features & Use Cases

Four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with explicit rules to prevent shortcuts.
Anti-patterns, red flags, and defense-in-depth recommendations to improve reliability across complex systems.
Real-world guidance for bugs, test failures, performance issues, and integration problems with a focus on evidence gathering and verification.

Quick Start

Load this skill and begin with Phase 1: Root Cause Investigation to ensure you identify the true cause before implementing fixes.

Frequently Asked Questions about systematic_debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is systematic debugging and how does it prevent symptom-focused fixes?▼

Systematic debugging is a structured approach that enforces root-cause investigation before proposing fixes. It prevents symptom-focused patches by requiring evidence gathering and pattern analysis to ensure the true cause is identified.

How do I debug software bugs using a four-phase workflow?▼

Debug software bugs by following a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. Explicit rules prevent shortcuts, requiring Phase 1 completion before proposing any fixes.

What is the best way to triage test failures and unexpected behavior in complex systems?▼

The best way to triage test failures is using defense-in-depth recommendations and structured evidence gathering. This approach provides real-world guidance for bugs, performance issues, and integration problems across complex systems.

Can I apply this debugging framework to performance issues and integration problems?▼

Yes, you can apply this debugging framework to performance issues and integration problems. It offers explicit rules, anti-patterns, and red flags to guide evidence gathering and verification for unexpected behavior.

Why should I avoid proposing fixes before completing root cause investigation?▼

You should avoid proposing fixes early because skipping root cause investigation leads to symptom-focused patches. The structured workflow enforces evidence gathering first, ensuring you address the true cause rather than surface-level behavior.

What are common anti-patterns and red flags to watch for during bug triage?▼

Common anti-patterns during bug triage include skipping evidence gathering or jumping to fixes before identifying the root cause. The framework highlights these red flags to improve reliability and enforce defensive practices across complex systems.