gstack-investigate

Root cause analysis prevents wasted effort by enforcing a staged workflow: investigate, analyze, hypothesize, then implement. This systematic approach ensures fixes are grounded in evidence rather than quick guesses.

Debugging unexpected behavior requires error- and behavior-driven triggering to initiate a root cause investigation. The process analyzes stack traces and failure context step by step to identify the actual source of the problem.

Systematic root cause investigation follows a staged workflow that gathers repo-aware context and prior learnings. It enforces the Iron Law: no fixes are implemented without identified root cause evidence.

Yes, investigating why a feature stopped working is triggered by requests to debug, fix, or explain unexpected behavior. The workflow leverages prior investigations and recent learnings to avoid repeating known pitfalls.

Yes, this root cause investigation workflow operates without requiring additional dependencies or components. It relies entirely on analyzing existing repo context, stack traces, and error reports to hypothesize and implement fixes.