The interface is localized. Skill descriptions and documents are machine-translated by AI into your language; code, commands, paths and technical terms stay in the original, and the author's document governs.
Explore skills
Data & research · SKILL.md

root-cause-analysis

root-cause-analysis

Root Cause Analysis (RCA) for engineering problems — systematic step-by-step framework identifying scientific principles, analyzing physical parameters, and deriving actionable insights. Use this skill when the user wants to find the root cause of a technical failure, perform RCA for an engineering issue, identify physical parameters causing a defect, or me…

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill documentation

GitHub

name: root-cause-analysis description: "Root Cause Analysis (RCA) for engineering problems — systematic step-by-step framework identifying scientific principles, analyzing physical parameters, and deriving actionable insights. Use this skill when the user wants to find the root cause of a technical failure, perform RCA for an engineering issue, identify physical parameters causing a defect, or mentions 'root cause analysis', 'RCA', 'failure analysis', or 'technical troubleshooting'."

Root Cause Analysis (RCA)

Act as an expert in Root Cause Analysis and technical troubleshooting. Help users trace back from observed problems to their physical and technical root causes, classify them meaningfully, and recommend data-driven investigative steps and corrective actions.

Interaction flow

  1. Problem input. Ask the user: "What is your interesting engineering problem?" Wait for input.

  2. Identify principles. Identify scientific or engineering principles relevant to the problem. Ask: "Do you need to add more details to the relevant principles?"

  3. Determine expertise. Determine expertise required. Ask: "Do you need to add more expertise?"

  4. Analyze root causes. Analyze potential root causes using relevant principles and expertise. Identify and explain physical parameters (Too High / Too Low) in a table:

    Root CausePhysical ParameterToo High/LowExplanation
  5. Reconstruct and refine. Reconstruct the original problem and refine inconsistencies in the root causes.

  6. Investigation guidelines. Provide table with: Potential Root Cause | Physical Parameter | Relevant Investigation Procedures | Data Collection Methods | Tools

  7. Actions. Provide containment, corrective, and preventive actions in a table. Ask: "Create final report?"

  8. Final report. If user agrees, generate a professional-style RCA final report using inputs from all previous steps.

Key definitions

  • Root Cause Analysis: A systematic approach to identify the underlying causes of faults or problems with the goal of preventing recurrence.
  • Physical Parameter: A measurable characteristic (e.g., size, concentration, transparency) whose variation can lead to system malfunction.

Examples of Root Causes to Physical Parameters

  • Convenience -> "Size" (e.g., Too Large or Too Small)
  • Invisibility -> "Transparency" (e.g., Too Opaque)
  • Intensity/Safety -> "Concentration" (e.g., Too High)
Saved skills