systematic▌

最少需要：

Structured debugging methodology that mandates root cause investigation before attempting any fixes. \n \n Four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with mandatory test cases \n Requires completing Phase 1 (evidence gathering, error analysis, data flow tracing) before proposing any fixes; blocks symptom-based patching \n Includes diagnostic instrumentation guidance for multi-component systems and backward call-stack tracing techniques

Conduct comprehensive, systematic literature reviews using multiple academic databases and generate professionally formatted documents.

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Structured debugging methodology that enforces root cause investigation before attempting any fix. \n \n Enforces four sequential phases: root cause investigation, pattern analysis, hypothesis testing, and implementation; skipping phases or proposing fixes prematurely triggers a redirect \n Includes diagnostic instrumentation patterns for multi-component systems, data flow tracing techniques, and explicit red flags that signal you're guessing rather than investigating \n Stops after three failed