skills.rest
ylxai
ylxaiCOMMUNITY
Explore all skills by this author →
GitHub

RootCauseAnalysis

Analyze incident reports to identify root causes and contributing factors.

2|Updated Apr 9, 2026
Search Tags:#root cause analysis#prevention#failure analysis#incident investigation#system thinking
One-click install
npx skills add https://github.com/ylxai/hafiportrait-saas --skill rootcauseanalysis-ylxai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: RootCauseAnalysis
Source: https://github.com/ylxai/hafiportrait-saas/tree/main/.kiro/skills/RootCauseAnalysis
Command: npx skills add https://github.com/ylxai/hafiportrait-saas --skill rootcauseanalysis-ylxai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in identifying the root causes of failures and preventing them through structured incident investigation methods.

Core Features & Use Cases

  • Structured Investigation: Utilizes various root cause analysis methods like 5 Whys, Fishbone, Postmortem, Fault Tree, and Kepner-Tregoe.
  • Systemic Learning: Focuses on systemic factors rather than individual blame.
  • Actionable Causes: Provides actionable contributing factors for effective remediation.
  • Use Case: After a production outage, use this Skill to analyze the incident, identify contributing factors, and implement preventive measures.

Quick Start

Run the RootCauseAnalysis skill for incident investigation and follow the workflow for identifying root causes.

Frequently Asked Questions about RootCauseAnalysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a root cause analysis for a production failure?▼

Use this Skill to conduct a root cause analysis by feeding incident reports into structured investigation workflows like 5 Whys and Fishbone, which identify actionable contributing factors for effective remediation.

What is the best way to investigate recurring defects without assigning individual blame?▼

Investigate recurring defects using systems thinking focused on systemic factors rather than individual blame, applying postmortem and Kepner-Tregoe methods to uncover actionable root causes for prevention.

Can I use the 5 Whys and Fishbone methods for software incident investigation?▼

Yes, you can use the 5 Whys and Fishbone methods for software incident investigation, as this Skill applies structured root cause analysis techniques to production failures and quality problems to generate remediation workflows.

Do I need knowledge of systems thinking to perform a failure analysis?▼

Yes, you need knowledge of root cause analysis methods and systems thinking to perform a failure analysis, as this Skill requires understanding systemic factors to identify actionable contributing factors for remediation.

When should I use a fault tree analysis for quality problems?▼

Use fault tree analysis for quality problems when you need to systematically identify root causes and contributing factors in recurring defects or production outages, providing structured workflows for remediation and prevention.

Related Skills

Explore More Software Engineering Skills→
jayteealaojayteealao

error-analysis

Analyze errors, stack traces, and logs to identify root causes and remediation steps.

Community
Basic
flonatflonat
127

lessons-learned

Run structured post-mortems to identify root causes and encode preventive measures.

Community
Advanced
InnerScopeHearingInnerScopeHearing

incident-runbook-templates

Create structured incident response runbooks with step-by-step procedures and escalation paths.

Official
Advanced
Adam-GuerinAdam-Guerin
1

postmortem-writing

Generate blameless postmortem documents with root cause analysis and action items.

Community
Intermediate