EN DE
← ← Back to Index

systematic-debugging

software-development › systematic-debugging v1.2.0
debugging troubleshooting problem-solving root-cause investigation

Description

4-phase root cause debugging: understand bugs before fixing.

Relevance to Our Projects

Standard protocol for every bug fix. Prevents random guessing and ensures we find the root cause before fixing. Includes the "Verification Before Completion" gate.

Pipeline

1🔎 Phase 1: Ursachenforschung — Fehler lesen, reproduzieren, Datenfluss verfolgen
2📐 Phase 2: Musteranalyse — Arbeitsende Beispiele finden, Unterschiede identifizieren
3🔬 Phase 3: Hypothesen & Testen — Falsifizierbare Theorien aufstellen, minimal testen
4🛠️ Phase 4: Implementierung — Regressionstest schreiben, Ursache beheben, verifizieren
5✅ Verifikation vor Abschluss — Tight Loop, Test-Suite, Szenario, Commit mit Belegen

Related Skills

test-driven-development plan subagent-driven-development

SKILL.md Preview

# Systematic Debugging

## Overview

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

**Violating the letter of this process is violating the spirit of debugging.**

## The Iron Law

```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```

If you haven't completed Phase 1, you cannot propose fixes.

## The Feedback Loop Rule

The feedback loop is the debugging work.

← ← Back to Index