systematic-debugging

Enforce a four-phase root-cause debugging workflow before proposing fixes.

1|Updated Mar 8, 2026

Search Tags:#debugging #troubleshooting #defense-in-depth #quality-assurance #root-cause #phase-based #root-cause-tracing

Ready to run

npx skills add https://github.com/tense-i/stock-market-simulator --skill systematic-debugging-tense-i

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill systematic-debugging-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging reduces time wasted on symptom fixes by enforcing a root-cause-first approach to bug resolution.

Core Features & Use Cases

Four-phase debugging workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to find durable fixes.
Anti-shortcut safeguards like explicit phase requirements, single-hypothesis rule, and rollback thinking to prevent rushed fixes.
Applicable to bugs, test failures, production incidents, and flaky behavior across software projects.

Quick Start

Follow Phase 1: perform root-cause investigation before attempting any fixes, and proceed through Phases 2-4 if root cause is identified.

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 find the root cause of bugs?▼

Systematic debugging is a disciplined approach that identifies the root cause of bugs before proposing fixes. It enforces a four-phase workflow to prevent symptom fixes and ensure durable issue resolution across software projects.

How do I troubleshoot flaky test failures without applying symptom fixes?▼

Troubleshoot flaky test failures by following a structured root-cause investigation process. You must complete the initial investigation phase to identify the underlying pattern before attempting any hypothesis testing or implementation of fixes.

Can I use this debugging workflow for production incidents and test failures?▼

Yes, this debugging workflow applies to production incidents, test failures, and flaky behavior across any technical issue. It provides a consistent root-cause-tracing methodology regardless of the software project environment.

What is the best way to prevent rushed fixes during root cause tracing?▼

Prevent rushed fixes during root cause tracing by applying anti-shortcut safeguards. These include explicit phase requirements, a single-hypothesis rule, and rollback thinking to ensure disciplined hypothesis testing before implementation.

Why does systematic debugging enforce a single-hypothesis rule?▼

Systematic debugging enforces a single-hypothesis rule to prevent scattered troubleshooting efforts. By testing one hypothesis at a time, you maintain focus during pattern analysis and ensure accurate root cause identification before moving to implementation.

What are the limitations of phase-based debugging for complex software issues?▼

Phase-based debugging requires completing explicit Phase 1 root cause investigation requirements before proceeding to pattern analysis and fixes. This strict anti-shortcut approach may slow down immediate symptom relief but ensures durable, long-term bug resolution.