workflow-debugging

Name: workflow-debugging
Availability: InStock
Author: akourmaz

Coordinate structured debugging workflows for reproducing, validating, and resolving software bugs.

Updated Mar 2, 2026

Search Tags:#debugging #regression #quality-assurance #reproduction #root-cause-analysis #bug-report

Ready to run

npx skills add https://github.com/akourmaz/translate2 --skill workflow-debugging-akourmaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-debugging
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/workflow-debugging
Command: npx skills add https://github.com/akourmaz/translate2 --skill workflow-debugging-akourmaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol standardizes how teams reproduce bugs, document facts, test hypotheses, and coordinate fixes to prevent recurrence.

Core Features & Use Cases

Reproduction documentation and evidence gathering
Hypothesis-driven debugging with structured reviews
Role-based delegation (coder, reviewer, meta-architect) and escalation
End-to-end fix planning, verification, and preventive measures
Suitable for defects, regressions, and unexpected behavior in software

Quick Start

Document initial reproducible steps and start the workflow using the defined roles to begin diagnosing the issue.

Frequently Asked Questions about workflow-debugging

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

FAQPage Schema

How do I structure a debugging workflow for reproducing and resolving software regressions?▼

A structured debugging workflow enforces sequential steps for bug reproduction, evidence gathering, hypothesis testing, fix planning, and verification to ensure safe, auditable resolutions for software regressions.

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

Hypothesis-driven debugging is a method of testing root-cause theories against gathered evidence before applying fixes. Use it for defects, unexpected behavior, or failing tests to prevent recurrence.

How do I document reproduction steps for a production incident or failing test?▼

Document initial reproducible steps by capturing the exact conditions and actions that trigger the unexpected behavior. This evidence gathering is the required starting point to diagnose the issue.

Can I assign specific roles like coder and reviewer when coordinating a bug fix?▼

Yes, the workflow supports role-based delegation including coder, reviewer, and meta-architect roles. This division of labor structures the debugging process and manages escalations for complex defects.

What's the best way to ensure a bug fix is verified and prevents future recurrence?▼

The best way to prevent recurrence is applying end-to-end fix planning and verification steps. This includes structured reviews and preventive measures after the root-cause analysis is complete.

Does this debugging workflow work for production incidents and failing tests across different software systems?▼

Yes, the workflow applies to defects, unexpected behavior, failing tests, and production incidents across software systems. It standardizes evidence gathering and resolution regardless of the specific platform.