mg-debug

Structured debugging coordinates QA, development, and security roles through a four-step cycle: reproduce, investigate, fix, and verify. It uses a spawn pattern to delegate specialized sub-tasks and a memory protocol to track progress across teams.

A structured debugging workflow standardizes bug resolution through sequential phases: reproduction, root-cause investigation, fixing, and verification. It enforces explicit output formats and team coordination to systematically address root causes.

Provide a bug description to trigger the debugging workflow. The system then coordinates the investigation, prompting QA to reproduce the issue and development to analyze the root cause before applying and verifying a fix.

Yes, the workflow uses a spawn pattern to delegate sub-tasks to specialized agents including QA, development, and security-engineer roles. This integrates security review directly into the root-cause analysis and fix verification cycle.

No external framework is required. Structured debugging operates independently without dependencies, managing team coordination internally through its memory protocol, explicit output formats, and spawn pattern across the four-step debug cycle.

A memory protocol tracks multi-role bug fixes to maintain context and progress across the reproduce, investigate, fix, and verify cycle. It ensures QA, dev, and security engineers share a continuous record, preventing lost context during root-cause analysis.