agentic-systematic-debugging

A reproduce-first debugging workflow requires establishing a reproducible failure state before root-cause analysis. This Skill enforces this process by guiding teams through problem definition, evidence gathering, hypothesis formation, and staged verification before patching.

Isolating the root cause of a production incident requires systematically gathering evidence and forming disciplined hypotheses. This Skill enforces a phase-driven workflow that locks the failure state and verifies the fix through structured testing.

Structuring hypothesis testing involves instrumenting the reproducible state, isolating the root cause, and locking the failure with tests. This Skill provides automated guardrails and a structured closure verification process to ensure testable fixes.

Yes, the reproduce-first debugging workflow applies across unit tests, integration tests, and production incidents. It ensures traceable outcomes and structured fixes regardless of the testing environment or failure scope.

Reproducing a failure before root-cause analysis avoids guesswork by providing a reliable state for evidence gathering. This Skill enforces reproduction attempts as a mandatory prerequisite before moving to hypothesis formation and patching.

Undisciplined debugging without automated guardrails often leads to untestable fixes and untraceable outcomes. This Skill prevents this by enforcing a staged workflow that requires failure locking and structured closure verification before resolving the bug.