devforgeai-rca

Root cause analysis using the 5 Whys methodology is driven end-to-end by guiding Claude through evidence-based phase progression to surface the underlying causes of framework breakdowns. It systematically collects evidence and generates an RCA-ready report with actionable recommendations.

A 5 Whys RCA workflow can investigate context violations, workflow state errors, and validation gaps across skills, commands, and subagents. It cross-analyzes these components to ensure every finding is grounded in phase-read files and documented evidence.

You can start an automated RCA workflow by invoking the command syntax with your incident identifier, which triggers Phase 0 and begins automated evidence collection. This initiates the structured 5 Whys progression to systematically analyze the breakdown.

Yes, automated RCA generates RCA documents that include prioritized recommendations, testing plans, and prevention strategies specifically for context violations. It ensures every recommendation is grounded in evidence collected from phase-read files during the analysis.

The best way to document root cause findings for workflow state errors is to use an automated RCA workflow that grounds every finding in phase-read files. This outputs a structured RCA-ready report containing prioritized recommendations, testing plans, and prevention strategies.

The 5 Whys root cause analysis operates with no external dependencies, running entirely within the Claude environment. It relies on reading phase-specific files and analyzing skills, commands, and subagents internally to validate evidence and progress through each phase.