systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: angelwings1997

Guide engineers through a four-phase debugging framework to locate root causes.

Updated Apr 11, 2026

Search Tags:#debugging #defense-in-depth #systematic #phases #hypothesis #root-cause

Ready to run

npx skills add https://github.com/AngelWings1997/altas --skill systematic-debugging-angelwings1997

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/AngelWings1997/altas/tree/main/altas-workflow/references/superpowers/systematic-debugging
Command: npx skills add https://github.com/AngelWings1997/altas --skill systematic-debugging-angelwings1997

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic Debugging provides a disciplined, four-phase framework to uncover root causes before implementing fixes, reducing wasted time and rework. Root-cause analysis is often skipped or rushed under pressure; this skill enforces a structured process to trace data flow, evaluate evidence, and prevent symptom-based fixes.

Core Features & Use Cases

Four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) that ensures traceability and repeatability.
Anti-patterns and defense-in-depth guidance to resist short-term shortcuts.
Practical guidance for debugging in time-constrained environments (on-call, CI, hotfix situations).

Quick Start

Load the skill and start with Phase 1: Root Cause Investigation, following the Step-by-Step checklist before proposing any 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 when should I use it?▼

Systematic debugging is a four-phase framework to uncover root causes before implementing fixes. Use it when symptoms are misleading or during time-constrained scenarios like on-call, CI, or hotfix situations where rushed analysis might lead to incorrect symptom-based fixes.

How do I find a root cause before applying a code fix?▼

To find a root cause, follow a structured four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This traces data flow and evaluates evidence to ensure you locate the true underlying issue before proposing any fixes.

What are common debugging anti-patterns to avoid under pressure?▼

Common debugging anti-patterns include skipping root-cause analysis and applying symptom-based shortcuts under time pressure. The framework resists these short-term fixes by enforcing defense-in-depth practices and requiring hypothesis evaluation before any implementation.

What's the best way to debug in production during an on-call incident?▼

The best way to debug in production during an on-call incident is using a phased framework that enforces traceability and repeatability. It guides you through pattern analysis and hypothesis testing to prevent rushed symptom-based fixes in high-pressure environments.

How do I test a debugging hypothesis systematically?▼

You test a debugging hypothesis systematically during Phase 3 of the workflow. After completing Root Cause Investigation and Pattern Analysis, you evaluate evidence and test your hypothesis before moving to Phase 4 to implement fixes and apply defense-in-depth practices.

Do I need any specific tools or dependencies for systematic debugging?▼

No specific tools or dependencies are required for systematic debugging. The framework is a structured process relying on references and logical phases—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—making it applicable across development, testing, and production environments.