메뉴
The 5 Why's is a root cause analysis technique that helps you identify the underlying cause of a problem by asking 'why' five times. This skill guides you through the process of applying the 5 Why's to a problem statement, allowing you to uncover the root cause and potential solutions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Generate and serve rich HTML companions to markdown discovery documents: paired markdown→HTML rendering (marked + mermaid + data-driven cytoscape/plotly fenced blocks), a vendored draw.io stencil library (~AWS/GCP/Azure/K8s SVG icons) for composing custom architecture diagrams, an injectable design-tokens brandpack, and a reliable localhost server for HTML that pulls pinned CDN libraries. Use when turning a review/architecture/cost markdown doc into an interactive HTML view, when a diagram needs real cloud provider icons, when serving local HTML that file:// breaks, or when building a data-driven graph/chart view. Skip when the deliverable is plain mermaid-in-markdown authoring with no HTML companion, or a Python-rendered architecture diagram image.
Introspect Claude Code sessions - query conversation history, tool usage, event trees, and costs. Use when reviewing past sessions, debugging failures, or recovering user intent post-compaction.
Documentation quality skill with three modes: (1) AUDIT — fan out parallel subagents to corroborate that docs still reflect the reality of the code (commands run, paths exist, signatures match, claims hold) and produce a drift report; (2) WRITE/IMPROVE — author or rewrite docs using the researched lens taxonomy (Diátaxis + distilled style principles from great OSS docs), optionally in the maintainer's personal voice; (3) RESTRUCTURE — reorganize an existing doc, spec, or plan file for structural readability (heading hierarchy, list/table discipline, whitespace rhythm, BLUF) without changing its claims. Use when the user asks to check/audit docs, fix stale docs, write or improve documentation, restructure a doc/spec/plan for readability, or says 'gooddocs'. Add 'voice' to the invocation to write in the maintainer's voice; default is the neutral researched style.
Render and analyze Mermaid.JS diagrams embedded in markdown files. Enforces visual complexity limits AND WCAG color-contrast requirements via automated analysis. Every diagram MUST derive its palette from `resources/color_theming.md` and pass `scripts/mermaid_contrast.ts` before being declared done. Use when creating or updating architecture diagrams, analyzing diagram complexity, improving documentation clarity, or exploring a codebase to produce dual-density architecture diagrams for a README.
Playbook for building and extending project-local developer CLIs and the recurring assets they generate, so the same patterns are never re-derived from scratch. Use when: scaffolding or adding a subcommand to a repo CLI (argparse/Typer, project-root discovery, packaged assets); generating a STATIC HTML single-page viewer (client-side SPA routing, collapsible sidebar, light/dark + rebrandable design-tokens theming, Cytoscape graph or Plotly chart, generate/serve, --inline single-file, --archive zip); templating GitHub Actions workflows from a base template (create/update/validate, trigger-path glob distillation, reusable composite-action assets); using git worktrees to act on another branch/ref safely; autogenerating SVG/PNG diagrams from a stencil pack; or automating sticky PR comments and embedding a CI-run artifact image in a PR comment. Skip for non-CLI app code, or one-off scripts with no reuse. Invoke as /cli or when the user names one of these patterns.
Script-driven gap-analysis planning: a deterministic state machine (pgsm.py) owns the phases of a tiered gap-analysis spec — bootstrap → refinement → validation → decomposition → execution → complete — with evidence-based transition gates, per-state-only instructions composed into a single prompt, durable pause/resume state, and session-log forensics. Use for long-horizon work-breakdown planning where phase tracking must not live in the model's head. Requires uv. Skip for quick single-file plans (use plan-gap) or when no plan document is wanted.
SOC 직업 분류 기준
| name | 5ys |
| description | The 5 Why's is a root cause analysis technique that helps you identify the underlying cause of a problem by asking 'why' five times. This skill guides you through the process of applying the 5 Why's to a problem statement, allowing you to uncover the root cause and potential solutions. |
| user-invocable | true |
push back on the current contextual issue, performing "The 5 Why's".
Force critically thinking about the problem with a broader macro view of the project instead of hyperfocusing on the *micro issue at hand.
Decisions MUST be made in the context of the whole project.
Often doing this will reveal that the "problem" is actually a symptom of a deeper issue, and that the real problem is something else entirely.
Also often doing will reveal we have already documented a decision framework and guiding values as a lens to make the decision, and that the "problem" is actually a non-issue because we have already made a decision on it.
We often already have agentic memories about the project structure and testing structure and the reasons for why it is structured that way.
think through unresolved issues by reflecting with "The 5 Why's" to correctly challenge the assumptions in the question at hand to make sure the decision is
grounded in the macro-context
