skills.rest
e-t-y-b
e-t-y-bOFFICIAL
Explore all skills by this author →
GitHub

debugging-protocol

Automate structured debugging workflows enforcing reproduction, single-variable testing, and escalation.

9|1|Updated Mar 21, 2026
Search Tags:#debugging#protocol#hypothesis#escalation#root-cause#one-variable#debugging-loop
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill debugging-protocol-e-t-y-b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-protocol
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/debugging-protocol
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill debugging-protocol-e-t-y-b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforces root-cause-first debugging discipline — reproduce, hypothesize, test ONE variable, and escalation after three failed hypotheses. Use when tests fail repeatedly, bugs resist reproduction, or fix attempts aren't converging on the cause.

Core Features & Use Cases

  • Root Cause First: Never fix symptoms; focus on underlying causes and prevent recurrence.
  • The Debugging Loop: Reproduce → Hypothesize → Test ONE variable → Verify → escalate after three failed hypotheses.
  • The One-Variable Rule: Change exactly one thing per test cycle to preserve traceability.
  • The Three-Failure Escalation Rule: Escalate after three failed hypotheses to ensure timely expertise.
  • Debugging State Tracking: Maintain a plan artifact with evidence, hypotheses, and outcomes.
  • Expert Escalation Paths: Clear routing between frontend, backend, database, and SRE specialists.
  • Post-debug obligations: regression tests, completion reports, and plan updates.

Quick Start

Reproduce the bug, propose hypotheses, test one variable at a time, and escalate after three failed attempts.

Frequently Asked Questions about debugging-protocol

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

FAQPage Schema
How do I debug a nondeterministic bug that resists reproduction?▼

The one-variable rule isolates root causes by changing exactly one factor per test cycle, ensuring traceable evidence and preventing confounding variables from obscuring the actual failure point.

What is the best way to stop fixing symptoms and find the root cause of failing tests?▼

Root-cause debugging enforces a structured loop of reproduction, hypothesis formulation, and single-variable testing to identify underlying causes and prevent symptom fixes and future recurrence.

When should I escalate a production incident during the debugging loop?▼

You should escalate a production incident after three failed hypotheses, triggering a routing path to frontend, backend, database, or SRE specialists to ensure timely expertise and rapid diagnosis.

Can I use this structured debugging workflow for both failing tests and production incidents?▼

Yes, this structured debugging workflow applies to failing tests, nondeterministic bugs, and production incidents where rapid, evidence-based diagnosis and root-cause-first remediation are required.

How do I track debugging state and evidence across multiple test cycles?▼

You track debugging state by maintaining a plan artifact that records reproduction evidence, formulated hypotheses, single-variable test outcomes, and escalation triggers throughout the debugging loop.

What post-debugging obligations are required after finding a root cause?▼

Post-debugging obligations require writing regression tests to verify the fix, generating a completion report, and updating the plan artifact to document the root-cause evidence and remediation.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
mrvladd-dmrvladd-d
53

mb-verify

Verify task completion against acceptance criteria and generate verification reports.

Community
Intermediate
webrix-aiwebrix-ai
1

incident-alerting

Configure incident alerting workflows with Slack and Grafana integrations.

Official
Intermediate
Busboom-FooBusboom-Foo

systematic-debugging

Executes a four-phase debugging workflow with evidence gathering and hypothesis testing.

Official
Advanced