Root Cause Finder
A systematic loop for identifying the root cause of code issues, bugs, or unexpected behavior through iterative investigation and analysis, ensuring develope…
This loop is republished with attribution. Full credit and the original content belong to the source linked above.
AI Skill Market Insights
Real data. Real impact.
Emerging
Developers
Kickoff Prompt
Copy this prompt and run it with your agent to start the loop.
Start the "Root Cause Finder" loop.
Goal: Identify root cause
Max iterations: 10
Between iterations run: investigation review
Exit when: Root cause documented
I'm experiencing an issue where [describe specific problem - e.g., 'my API returns 500 errors when processing POST requests']. The error occurs in [component/context] and started happening after [recent changes or timeline if applicable]. I suspect it might be related to [initial hypothesis], but want to systematically identify the root cause. Can you investigate this step by step?
Self-pace this loop. After each iteration, run `investigation review` and evaluate the output, and only continue if the exit condition is not met (Root cause documented). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.