022-root-cause-analysis
仓库创建 2025年2月9日最近提交 14 小时前SkillHot 收录 2 小时前
▸ 精选理由
适合需要深入诊断并避免治标不治本场景。
这个 Skill 做什么
用五个为什么、鱼骨图等方法查找问题根因并识别约束。
帮你把表面问题往下追,找到真正的根因而不是临时修补,用 Five Whys、Fishbone(Ishikawa)和 Current Reality Tree 等工具做推演。适合在提出解决方案前先确认问题来源和限制时用,避免盲目修补症状。特别之处是除了找原因,还会识别约束点,帮助找到能带来长期改进的切入口。
▸ 展开 SKILL.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 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
423
Stars
88
Forks
40
仓库内 Skill
+9
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/jabrena/plinth/main/skills/022-root-cause-analysis/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/022-root-cause-analysis/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Root Cause Analysis 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?** - Five Whys for a linear causal chain from a symptom to a root cause - Fishbone (Ishikawa) for categorized candidate causes across multiple dimensions - Current Reality Tree for interconnected causes and effects with a small number of core problems - Constraint identification for the limiting factor holding the current state in place - Choosing the technique(s) proportionate to the problem's complexity - Feeding root-cause findings in
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有