analyst-diagnostics

Root cause analysis using the Five Whys technique involves repeatedly asking why a problem occurred to drill down to its fundamental cause. This Skill applies that method alongside Ishikawa diagrams to your project documentation, identifying core issues and organizing findings into a structured report.

The best way to run prospective change analysis is to apply structured methodologies like Lovebug analysis to identify potential causes and barriers before changes occur. This Skill processes your documentation to categorize risks and pinpoint exact causes, outputting detailed findings for proactive mitigation.

Yes, you can use Ishikawa fishbone diagrams for incident retrospectives. This Skill applies Ishikawa methodology to your project documentation to visually map out problem categories, combined with Lovebug analysis to reveal root causes and suggest actionable fixes for future prevention.

Effective problem definition and diagnostics require clear documentation of findings related to the incident or project change. This Skill analyzes these text inputs to extract perceived problems, categorize them accurately, and apply root cause analysis techniques to generate a comprehensive summary table.

Lovebug analysis identifies causes and barriers by examining project documentation to systematically separate driving factors from obstacles. This Skill uses the Lovebug method alongside the Five Whys to diagnose problems, determining fundamental reasons and providing structured reporting within your project README.