systematic-debugging

Coordinate root-cause investigation across software stacks with a four-phase debugging workflow.

3|Updated Dec 30, 2025

Search Tags:#debugging #troubleshooting #root-cause #pattern-analysis #data-flow #hypothesis-testing

Ready to run

npx skills add https://github.com/martin-janci/claude-marketplace --skill systematic-debugging-martin-janci

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/martin-janci/claude-marketplace/tree/main/plugins/dev-agents/skills/systematic-debugging
Command: npx skills add https://github.com/martin-janci/claude-marketplace --skill systematic-debugging-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software teams often chase symptoms instead of root causes, leading to prolonged outages and risky, guess-based fixes. Systematic Debugging provides a disciplined four-phase approach to ensure root-cause investigation precedes implementation.

Core Features & Use Cases

Four-phase framework: root-cause investigation, pattern analysis, hypothesis testing, implementation.
Evidence-based debugging with structured data-flow tracing and diagnostic instrumentation.
Guidance on when to stop, escalate, and validate fixes with tests.
Integrates with existing debugging workflows to reduce MTTR and improve reliability.

Quick Start

Initiate the four-phase debugging workflow on the current issue before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of a software bug instead of just fixing symptoms?▼

To find the root cause of a software bug, apply a four-phase systematic debugging framework that enforces evidence gathering, data-flow tracing, and hypothesis testing before any implementation. This prevents guess-based fixes and ensures you resolve the underlying issue.

What is the best way to debug multi-component software stack incidents?▼

The best way to debug multi-component software stack incidents is using a structured four-phase workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation. This coordinates error messages and data traces across the stack to reduce mean time to resolution.

How do I systematically troubleshoot errors using hypothesis testing?▼

Systematically troubleshoot errors using hypothesis testing by forming data-driven theories during pattern analysis, then validating them through diagnostic instrumentation. The framework requires test-driven verification of your hypotheses before moving to the implementation phase.

When should I escalate a debugging issue instead of continuing to investigate?▼

You should escalate a debugging issue when the systematic four-phase workflow provides built-in guardrails indicating that root-cause investigation has hit a dead end. The framework offers explicit guidance on when to stop investigating and escalate the incident scenario.

How do I prevent ungrounded fixes during incident troubleshooting?▼

Prevent ungrounded fixes during incident troubleshooting by using a debugging framework with strict guardrails that require test-driven verification and pattern analysis. This ensures fixes are grounded in evidence from data traces rather than risky guesses.

Can I integrate systematic debugging into my existing incident response workflows?▼

Yes, you can integrate systematic debugging into existing incident response workflows. The four-phase framework operates as a coordinating layer for real-time debugging, enhancing your current processes with structured data-flow tracing to improve overall reliability.