Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ace3000chao/book2startup --skill 005-five-whysgit clone --depth 1 https://github.com/ace3000chao/book2startupWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ace3000chao/book2startup/005-five-whys)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/005-five-whys"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/005-five-whys/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ace3000chao/book2startup/005-five-whys"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/005-five-whys.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.01332 |
| Opus 5 | $0.00028 | $0.00666 |
| Sonnet 5 | $0.00011 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
five-whys scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: 五个为什么分析
Metadata
- ID: leanstartup-005
- 类型: framework
- 来源: 《精益创业》第十一章
- 验证状态: ✅ 三重验证通过（V1: 11章完整说明+案例, V2: 团队日常高频, V3: 反常识）
R — Reading（原文引用）
"五个为什么是一种根源分析方法，通过不断追问'为什么'来找到问题的根本原因，而非仅仅解决表面症状。"
"如果我们不持续追问根本原因，同样的问题会反复出现，消耗团队精力。"
I — Interpretation（方法论骨架）
五个为什么的核心洞察：问题的表象往往不是真正的问题。
当你遇到问题时，99%的人在想"怎么解决这个"，而只有1%的人在问"为什么会出现这个问题"。
不追问根本原因的后果：
- 每次问题出现就用补丁解决（治标不治本）
- 同样的问题在不同时间、不同形式反复出现
- 团队精力被反复消耗在"救火"上
按比例投入：大问题大投入，小问题小投入。不需要为所有问题都追5个为什么。
A1 — Past Application（书中案例）
IMVU的产品缺陷处理：每次产品出问题，团队就快速打补丁。但通过五个为什么分析发现，根本原因是"测试流程没有覆盖实际用户场景"——不是"某个功能有bug"，而是"整个质量保障体系有问题"。修复了这个根本问题后，缺陷率大幅下降。
丰田的精益生产起源：大野耐一用五个为什么识别出工厂效率低下的根本原因不是设备问题，而是"工人缺乏改进权限"——这直接促成了丰田生产系统的建立。
A2 — Future Trigger（何时调用）
当你听到以下问题时，就应该调用这个Skill：
- "这个问题我们已经修复过3次了，怎么又出现了？"
- "团队总在加班救火，但问题似乎永远解决不完"
- "某个指标突然变差，但不知道是什么原因"
- "每次开会都在讨论同一个问题"
- "我们花了很长时间做优化，但效果不明显"
E — Execution（可执行步骤）
步骤1：识别需要分析的问题
选择标准：
- 这个问题是否重复出现？（出现1次可能是偶然，3次以上就是系统性问题）
- 这个问题的影响有多大？（大影响值得深挖，小问题不值得过度分析）
- 团队是否倾向于用临时补丁解决？（是的话需要追问）
步骤2：开始追问（从问题陈述开始）
"为什么这个问题发生了？" 记录答案。
"为什么那个原因导致了这个问题？" 记录答案。
继续，直到问满5次，或者答案已经是"这是流程/文化/架构问题"
注意：每次追问的答案必须是可操作的具体原因，不能是模糊的"人为疏忽"或"沟通不畅"。
步骤3：按比例投入资源
| 问题严重程度 | 投入资源 | 预期 |
|---|---|---|
| 影响核心业务/大量用户 | 大投入，彻底修复 | 根除 |
| 影响部分用户/中等频率 | 中等投入，流程改进 | 大幅减少 |
| 偶发/影响小 | 小投入，简单处理 | 接受现状 |
步骤4：防止历史包袱
不要把"历史包袱"放进五个为什么流程：
- "这个问题存在太久了，所以不用分析"
- "当时的情况和现在不一样"
- "以前的人做的决策我们不要追究"
只关注现在和未来：这个流程/体系/方法在当前是否还在产生问题？
步骤5：指定负责人
每个五个为什么分析必须指定一个**"五个为什么负责人"**：
- 负责追踪问题是否被根本性解决
- 负责在问题再次出现时启动新一轮分析
- 负责向团队报告改进效果
B — Boundary（何时不适用）
| 不适用场景 | 原因 |
|---|---|
| 需要立即处理的紧急故障 | 这时候需要快速止血，之后再复盘分析 |
| 问题原因已经明确（如明显的资源缺失） | 不需要追5个为什么，直接解决 |
| 跨部门的复杂系统问题 | 需要更结构化的分析方法 |
作者盲点提醒：五个为什么可能被滥用——有人会用它"追责"而非"解决问题"。这会让团队害怕暴露问题，反而掩盖了真正的问题。健康的五个为什么文化需要"对事不对人"的心理安全感。
关联Skills
- 小批量原则 — 小批量能让问题快速暴露，而不是等几个星期才发现
- 创新沙盒 — 创新沙盒用五个为什么建立自适应组织
- 转型决策树 — 五个为什么是判断"转型根本原因"的重要工具
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 98 lines · 57 tokens per session scan A de8b599591c2
five-whys is a skill published in the GitHub repository ace3000chao/book2startup (80 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,332 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.