debug-workflow

Guide hypothesis-driven debugging through five investigation phases to verified fixes.

1|Updated Apr 20, 2026

Search Tags:#debugging #traceability #triage #root-cause #reproduction #hypotheses #binary-search

Ready to run

npx skills add https://github.com/IndianBoy42/dot-opencode --skill debug-workflow-indianboy42

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-workflow
Source: https://github.com/IndianBoy42/dot-opencode/tree/main/skills/debug-workflow
Command: npx skills add https://github.com/IndianBoy42/dot-opencode --skill debug-workflow-indianboy42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This approach provides a structured, hypothesis-driven debugging workflow to systematically isolate root causes and reduce debugging time.

Core Features & Use Cases

Phase-based methodology: Isolate & Gather Context, Generate Hypotheses, Iterative Investigation, Confirm Root Cause, Fix & Verify.
Escalation criteria to involve higher-tier agents when architectural changes are needed.
Context management guidance to track hypotheses and preserve investigation state.

Quick Start

Describe the failure scenario, reproduce it with a minimal test case, and follow the hypothesis-driven phases to locate and fix the root cause.

Frequently Asked Questions about debug-workflow

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

FAQPage Schema

What is hypothesis-driven debugging and when should I use it?▼

A hypothesis-driven debugging workflow structures investigation into five phases: Isolate & Gather Context, Generate Hypotheses, Iterative Investigation, Confirm Root Cause, and Fix & Verify. It guides users from failure onset to verified fixes through systematic investigation.

How do I debug complex, multi-system bugs systematically?▼

Debug complex multi-system bugs by gathering context, generating hypotheses, and applying controlled experimentation. This structured workflow defines escalation criteria and context-management practices to track hypotheses and preserve investigation state.

What's the best way to reproduce a failure scenario for root-cause analysis?▼

The best way to reproduce a failure scenario for root-cause analysis is to describe the failure, reproduce it with a minimal test case, and follow the hypothesis-driven phases to locate and fix the root cause.

Does this debugging workflow support escalation for architectural changes?▼

Yes, the debugging workflow includes explicit escalation criteria to involve higher-tier agents when architectural changes are needed during the investigation.

How does binary-search methodology apply to software triage and traceability?▼

Binary-search methodology applies to software triage by isolating failure points through controlled experimentation within the iterative investigation phase, efficiently narrowing down variables in complex multi-system bugs.

When should I not use hypothesis-driven debugging?▼

Hypothesis-driven debugging should not be used for simple, single-system errors where traditional error tracing quickly identifies the issue. It is designed specifically for complex, multi-system bugs requiring structured investigation.