skills.rest
Ibrahim-3d
Ibrahim-3dCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide engineers through a four-phase debugging workflow to root-cause bugs and failures.

371|38|Updated Feb 17, 2026
Search Tags:#testing#troubleshooting#defense-in-depth#phases#root-cause#systematic-debugging
One-click install
npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill systematic-debugging-ibrahim-3d
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill systematic-debugging-ibrahim-3d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically root-cause bugs and failures to avoid symptom fixes and wasted time.

Core Features & Use Cases

  • Four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Anti-patterns, defense-in-depth, and stack-trace instrumentation guidelines to ensure robust debugging.
  • Use cases include debugging production incidents, flaky tests, and complex multi-component failures.

Quick Start

Read the skill and apply Phase 1, then Phase 2, Phase 3, and Phase 4 in order for repeatable, verifiable fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging workflow for root-causing production incidents?▼

A systematic debugging workflow root-causes production incidents through strict phase ordering: evidence gathering, pattern analysis, hypothesis testing, and implementation verification to prevent symptom-only fixes.

How do I debug flaky tests without fixing symptoms?▼

Debug flaky tests by following a four-phase framework: root cause investigation, pattern analysis, hypothesis and testing, and implementation, ensuring you verify the actual fix rather than patching symptoms.

What's the best way to troubleshoot complex multi-component failures?▼

Troubleshoot complex multi-component failures using a structured approach that gathers evidence, analyzes patterns, tests hypotheses, and implements verified fixes, supported by stack-trace instrumentation and defense-in-depth guidelines.

Can I use this systematic debugging framework for test failures under time pressure?▼

Yes, this debugging framework is specifically applicable to test failures under time pressure, providing a repeatable four-phase process to identify root causes quickly and avoid wasted time on incomplete fixes.

Why should I not skip phases when debugging software failures?▼

Skipping phases risks implementing symptom-only fixes because strict phase ordering ensures you gather evidence, analyze patterns, and test hypotheses before implementation, preventing wasted time and recurring bugs.

When do I need defense-in-depth and stack-trace instrumentation during debugging?▼

Apply defense-in-depth and stack-trace instrumentation during the implementation phase to ensure robust debugging and prevent future regressions after root-causing the original failure.

Related Skills

Explore More Software Engineering Skills→
kunalrawat425kunalrawat425

gstack-openclaw-investigate

Diagnose bugs by performing root-cause analysis before applying fixes.

Community
Advanced
lespacemanlespaceman
4

systematic-debugging

Identify root causes of bugs through a four-phase debugging process.

Community
Advanced
NeuveAINeuveAI
1

debug-agent

Identify bug root causes by collecting NDJSON logs and testing hypotheses.

Official
Advanced
doitiandoitian
14

systematic-debugging

Enforce a four-phase root-cause debugging process for code and tests.

Community
Advanced