- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add jabrena/plinth --skill 022-root-cause-analysis -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add jabrena/plinth --skill 022-root-cause-analysis -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add jabrena/plinth --skill 022-root-cause-analysis -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add jabrena/plinth --skill 022-root-cause-analysis -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/jabrena/plinth/tree/HEAD/skills/022-root-cause-analysisDari penerbit
Guide the identification of root causes, not symptoms, for a framed problem, using Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This is an interactive SKILL.
What is covered in this Skill?
023-assumption-analysis and the remaining Functional Specification lensesDistinguish root causes from symptoms before recommending a fix. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly.
references/022-root-cause-analysis.md before applying Root Cause Analysis guidanceRead references/022-root-cause-analysis.md, then identify the symptom(s) evidenced by the problem frame.
Chain "why" questions from the symptom toward an evidenced root cause, stopping when further "why" steps would require guessing.
Organize candidate causes into categories when more than one causal dimension (people, process, technology, environment) is plausible.
Connect multiple symptoms to a small number of shared core problems through cause-effect relationships when the symptoms appear related.
Name the constraint limiting the current state, distinct from the most visible or most recently reported cause.
Report findings using Five Whys, Fishbone, Current Reality Tree, and the identified constraint, and flag any finding left open pending a clarifying answer.
For detailed guidance, examples, and constraints, see references/022-root-cause-analysis.md.
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trig
---name: 022-root-cause-analysisdescription: Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys…---# skills/022-root-cause-analysis/SKILL.mdRingkasan umum
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the root cause of a problem before proposing a fix. Part of Plinth Toolkit
FAQ
Unduh skills/022-root-cause-analysis/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/jabrena/plinth.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.