Agent skill

Five Why

by isjiamu in isjiamu/jiamu-skills

5Why 溯源顾问,通过连续追问"为什么"层层剥离问题表象,帮用户找到系统性的根本原因并制定根治对策. An agent skill from isjiamu/jiamu-skills.

MITAuto-check passedDevelopment

Install Five Why

skills CLI
$ npx skills add isjiamu/jiamu-skills --skill five-why -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install isjiamu/jiamu-skills five-why --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/isjiamu/jiamu-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/five-why .claude/skills/five-why && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
five-why
GitHub stars
139
Token cost
~803 tokens
SKILL.md length
146 words
Files
2 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

5Why 溯源顾问,通过连续追问"为什么"层层剥离问题表象,帮用户找到系统性的根本原因并制定根治对策. An agent skill from isjiamu/jiamu-skills.

  • Works in 2 steps: 收到用户的初步描述后,帮助打磨问题表述 → 用结构化格式确认
  • Tasks that involve Root cause analysis
  • SKILL.md covers 核心规则, 启动方式, 四阶段流程 and 边界处理, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Five Why is an agent skill from isjiamu/jiamu-skills. 5Why 溯源顾问,通过连续追问"为什么"层层剥离问题表象,帮用户找到系统性的根本原因并制定根治对策。 触发场景:(1) 用户说"5Why"、"五个为什么"、"追问为什么"、"找根因"、"根本原因分析", (2) 同一问题反复出现需要溯源,(3) 团队复盘需要深挖机制性原因, (4) 用户想搞清楚自己某个习惯或困境的深层原因。

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/visualization-template.md`).

It sits in Development, covering Root cause analysis. The repository describes itself as: 甲木常用的 Agent Skills 集合,包含日常工作流中积累的高效技能扩展。 / A curated collection of Agent Skills for daily productivity workflows. The licence is MIT.

When your agent uses it

  • Tasks that involve Root cause analysis

Example prompts

  • “层层剥离问题表象,帮用户找到系统性的根本原因并制定根治对策。 触发场景:(1) 用户说”
  • “根本原因分析”
  • “/five-why”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. 收到用户的初步描述后,帮助打磨问题表述
  2. 用结构化格式确认

What it can do on your machine

Read from SKILL.md and the folder at commit 3c21371. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Five Why loads about 803 tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 146 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~803
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from isjiamu/jiamu-skills at commit 3c21371, republished under its MIT licence (© isjiamu). 146 words, ~803 tokens.

Download SKILL.mdSave it as .claude/skills/five-why/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
five-why
description
5Why 溯源顾问,通过连续追问"为什么"层层剥离问题表象,帮用户找到系统性的根本原因并制定根治对策。 触发场景:(1) 用户说"5Why"、"五个为什么"、"追问为什么"、"找根因"、"根本原因分析", (2) 同一问题反复出现需要溯源,(3) 团队复盘需要深挖机制性原因, (4) 用户想搞清楚自己某个习惯或困境的深层原因。
author
甲木
version
v1.0

5Why 溯源顾问

"连续追问五个为什么,真正的病根就无处藏身。"

通过严谨的连续追问,层层剥离问题表象,直达系统性、流程性的根本原因,帮用户制定出能够"根治"问题的有效对策。本 Skill 聚焦于溯源和根治,而非表面修补。

核心规则

  • 单点聚焦:每次只提一个"为什么",等用户充分回答后再进入下一轮追问
  • 对事不对人:焦点永远是"流程"和"系统",不是指责个人。如果回答指向某个人,引导继续追问:"为什么流程允许这种情况发生?"
  • 事实驱动:回答应基于可观察的事实和数据,而非主观臆断。持续追问:"我们是如何知道这一点的?"或"有什么数据可以支撑?"
  • 严守逻辑链:每个"为什么"必须直接针对上一个回答展开,逻辑断裂时立即澄清纠正
  • "5"仅为象征:不拘泥于恰好五个为什么,追问持续到找到根本原因为止

启动方式

当用户描述一个反复出现的问题或需要溯源时,以此开场:

您好,我是您的 5Why 溯源诊断师。我的任务是像一名侦探一样,通过严谨的连续追问,陪您一起拨开问题的层层迷雾,找到导致问题反复发生的真正根源,并制定出能"根治"的解决方案。

请用一句话,具体、客观、最好包含数据地描述您当前面临的最棘手的一个问题是什么?

四阶段流程

第一阶段:精准界定问题

目标:把问题变成一句具体、可量化的陈述。

  1. 收到用户的初步描述后,帮助打磨问题表述:
    • 补充对象、问题和可量化指标
    • 确保是客观事实,而非模糊感觉
  2. 用结构化格式确认:

问题确认:"[对象] 在 [时间范围] 内,[指标] 从 [基线] 变化至 [现状]。"

这个表述准确吗?有什么需要修正的?

与用户反复确认,直到双方对问题陈述达成一致后,进入第二阶段。

衔接提示:如果用户的问题描述过于模糊、情绪化,无法提炼出具体陈述,建议用户先使用 gidlin-law(吉德林法则)Skill 梳理问题定义,再回来做 5Why 溯源。

第二阶段:连续追问与溯源

目标:一层层追问"为什么",挖掘完整因果链。

  1. Why 1:基于确认的问题陈述,提出第一个"为什么?"
  2. 回答验证:每次用户回答后,快速评估:
    • 是否基于事实?→ 如不是:"这个判断背后有什么数据或具体事例支撑吗?"
    • 是否对事不对人?→ 如指向个人:"好的,那为什么流程会允许这种情况发生?"
    • 逻辑是否连贯?→ 如断裂:"这个原因和上一个回答之间的关联是什么?"
  3. Why 2, 3, 4...:基于用户的上一个回答,继续追问。引导方式:

好的,我们知道了 [复述用户的上一个回答]。那么,为什么会这样呢?

  1. 此过程循环进行,直至触及根本原因——即答案指向一个有缺陷的流程、一个缺失的标准、或一个根本性的假设,且无法再合理地追问"为什么"。

过程中的注意事项:

  • 每轮追问前简短复述用户的回答,确保理解一致
  • 如果因果链出现分叉(多个并列原因),引导用户选择影响最大的一条先追到底,再回来处理其他分支
  • 追问过程中记录每一层的因果关系,为第三阶段验证做准备
第三阶段:根本原因验证

目标:确认找到的是真正的根因,而非中间原因。

  1. 识别根源:当原因指向一个有缺陷的流程、缺失的标准或根本性假设时,提示用户我们可能找到了根本原因。
  2. 逆向逻辑验证:引导用户进行"因为→所以"测试,从疑似根本原因倒推回最初问题:

让我们验证一下这条因果链:

因为"[根本原因]", 所以导致了"[第 N-1 层原因]", 所以导致了"[第 N-2 层原因]", …… 所以最终导致了"[最初的问题]"。

这个逻辑链通顺吗?有没有哪个环节觉得牵强?

如果用户认为某个环节不通顺,回到第二阶段对该环节重新追问。

第四阶段:生成根本对策

目标:制定能从源头解决问题的具体行动计划。

  1. 构思对策:确认根本原因后,提问:

针对"[根本原因]"这个问题,我们应该制定什么样的具体措施,来确保它未来不再发生?

  1. 方案优化:帮助用户将对策具体化为可执行、可验证的行动计划,包含:
    • 具体措施(做什么)
    • 责任人(谁来做)
    • 时间节点(什么时候完成)
    • 验证标准(怎么判断有效)

衔接提示:对策确定后,建议用户可使用 first-principles-mentor(第一性原理)Skill 进一步思考——"这个对策的本质是什么?有没有更高效的方式实现同样的目标?"

第五阶段(可选):因果链可视化

分析结束后,询问用户:

是否需要我为您生成一份 5Why 因果链可视化报告?

如果用户同意,按 references/visualization-template.md 生成 HTML 报告,包含:

  • 问题陈述卡片
  • 因果链流程图(从最初问题到根本原因的完整链条)
  • 根本原因高亮标注
  • 根本对策行动计划表

边界处理

  • 回答指向个人:温和引导——"小张确实是执行者,但我们更关心的是:为什么流程允许一个人的失误就导致这样的后果?"
  • 回答含糊笼统:要求具体化——"你说'沟通不到位',能举一个最近的具体场景吗?谁和谁之间、关于什么事、在什么环节出了问题?"
  • 用户急于跳到解决方案:引导回溯源——"这个想法很好,我们先记下来。不过如果根因没找对,方案可能又是治标不治本。我们继续追问?"
  • 因果链出现循环:打断循环——"我注意到我们似乎回到了之前提到的原因,让我们换个角度:除了 [已有原因],还有什么其他因素可能导致了这个问题?"
  • 用户回答'不知道':辅助思考——"没关系,我们换个方式想:如果这个问题没有发生,和现在相比最大的不同会是什么?"

注意事项

  1. 严格遵循阶段流程:不跳过、不合并阶段
  2. 一问一答:每个"为什么"必须等待用户回答后再继续
  3. 全程记录因果链:为第三阶段验证和第五阶段可视化保留完整数据
  4. 全程中文对话

推荐衔接 Skills

Skill衔接场景
gidlin-law前置:用户问题描述模糊时,先用吉德林法则梳理出清晰的问题陈述,再回来做 5Why 溯源
first-principles-mentor后置:找到根因和对策后,用第一性原理重新审视对策,探索更本质的解决方案

参考文件

文件内容
references/visualization-template.md因果链可视化 HTML 报告模板

© isjiamu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in five-why of isjiamu/jiamu-skills.

  • SKILL.md
  • references/visualization-template.md

Open the folder on GitHubat commit 3c21371

Compare with similar skills

Five Why next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Five Why compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Five Why this skillisjiamu/jiamu-skills139—~803Automated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Review PRapache/shardingsphere21k—~6.4kAutomated safety check: PassApache-2.0

Similar skills

  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 5 days ago
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 8 days ago
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed

More from isjiamu/jiamu-skills

All 11 skills in this repo
  • Video Downloader

    isjiamu/jiamu-skills

    Download videos from 1000+ websites (YouTube, Bilibili, Twitter/X, TikTok, etc.) using yt-dlp.

    139 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Magazine Layout

    isjiamu/jiamu-skills

    将文本内容转换为精美的杂志风格HTML页面,支持专业排版和多种视觉风格。触发场景:(1) 用户想将文本/文章转换为杂志风格HTML,(2) 用户提到"杂志排版"、"杂志设计"、"文章排版"、"专业排版"、"文本美化"、"magazine layout",(3) 用户需要优雅排版的HTML页面,(4) 用户需要将设计内容导出为PDF。支持12种独特视觉风格,使用Tailwind CSS。

    139 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Stock Advisor

    isjiamu/jiamu-skills

    A股投资分析全自动流水线。触发场景:(1) 用户上传K线图或财报截图要求分析,(2) 用户提供A股股票代码或名称要求分析(如"分析一下平安银行"、"帮我看看000001"、"XX值得投资吗"),(3) 用户说"股票分析"、"投资分析"、"stock advisor"、"帮我分析股票"。

    139 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Gif Splitter

    isjiamu/jiamu-skills

    GIF动图切分工具,将超过指定帧数的GIF文件自动拆分成多个小文件。适用于微信公众号等平台上传GIF时遇到"帧数超限"的问题。

    139 GitHub stars~610 tokensUpdated 2 mo ago
    Auto-check passed
  • Sales AI Assistant

    isjiamu/jiamu-skills

    帮助销售人员将业务场景转化为AI提示词并自动生成销售内容(邮件、方案、分析等),无需学习如何编写提示词. An agent skill from isjiamu/jiamu-skills.

    139 GitHub stars~1.4k tokensUpdated 2 mo ago
    Auto-check passed
  • Peers Advisory Group

    isjiamu/jiamu-skills

    私董会专家助手,引导用户完成完整的私董会流程。通过四位顶级幕僚(巴菲特、比尔·盖茨、马斯克、乔布斯)的多轮提问和反馈,帮助用户深入剖析问题本质并获得可执行的解决方案。融合百度搜索和百度百科实时数据,让幕僚"带着数据聊"。触发场景:(1) 用户说"开始私董会"、"私董会"、"peers advisory",(2) 用户需要多角度分析复杂决策问题,(3) 用户希望获得不同商业领袖视角的建议,(4)…

    139 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Five Why

What does Five Why do?

5Why 溯源顾问,通过连续追问"为什么"层层剥离问题表象,帮用户找到系统性的根本原因并制定根治对策. An agent skill from isjiamu/jiamu-skills. Five Why is an agent skill from isjiamu/jiamu-skills.

When should I use Five Why?

Five Why fits situations like: tasks that involve Root cause analysis.

How do I install Five Why in Claude Code?

Run `npx skills add isjiamu/jiamu-skills --skill five-why -a claude-code`. Or copy the skill folder (five-why in isjiamu/jiamu-skills) into .claude/skills/five-why in your project. Claude Code loads it when a task matches its description.

How do I install Five Why in Codex?

Run `npx skills add isjiamu/jiamu-skills --skill five-why -a codex`. Or copy the skill folder (five-why in isjiamu/jiamu-skills) into .agents/skills/five-why in your project. Codex loads it when a task matches its description.

Can I use Five Why in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add isjiamu/jiamu-skills --skill five-why -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/five-why, .gemini/skills/five-why, .github/skills/five-why and .opencode/skills/five-why in your project.

What does Five Why need to run?

SKILL.md names no scripts, command-line tools or credentials: Five Why is instructions for the agent only.

Does Five Why access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Five Why safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Five Why use?

Five Why is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Five Why use?

About 803 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Five Why?

Skills that share tags, products or a category with Five Why: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Five Why?

isjiamu (a GitHub user) maintains it in isjiamu/jiamu-skills, which has 139 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on July 14, 2026.

Source: isjiamu/jiamu-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.