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 mentions 'root cause analysis', 'RCA', 'failure analysis', or 'technical troubleshooting'.
소스 정보
- 저장소
- Robert-Adunka/triz-skills
- 최근 소스 활동
- 2026년 5월 6일 21:11
- 감지된 SKILL.md 언어
- 영어
- 스타
- 11
- 포크
- 2
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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'.
<!--
Based on the Root Cause Analysis GPT Prompt
Copyright (c) 2025 Tanasak Pheunghua
Licensed under the MIT License — see LICENSE in the repository root.
-->
# 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 Cause | Physical Parameter | Too High/Low | Explanation |
|---|---|---|---|
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)
GitHub에서 보기