five-whys
/five-whys
Przeprowadza analizę Pięciu Dlaczego krok po kroku, aż do przyczyn źródłowych, i rysuje czytelny wykres z miarami, w czacie lub na tablicy.
- Autor
- GoodRelax ↗
- Repozytorium
- gr-whiteboard ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Przeprowadza analizę Pięciu Dlaczego krok po kroku, aż do przyczyn źródłowych, i rysuje czytelny wykres z miarami, w czacie lub na tablicy.
Oryginalny opis (EN)
Run a Five Whys analysis (Toyota) with the person. It asks why, one step at a time, checks each answer, and walks each branch down to its root cause, then draws a clean chart with the measures. It works in the chat, and on the local whiteboard of this plugin (server board-control) when the person asks for it or agrees to it. Use when the user types /gr-whiteboard:five-whys, asks for a Five Whys (Nazenaze) analysis, or when consult-on-board or issue-driven picks it.
Jak działa
- Board
- Checks
- Clean chart
Podgląd SKILL.md
---
name: five-whys
description: Run a Five Whys analysis (Toyota) with the person. It asks why, one step at a time, checks each answer, and walks each branch down to its root cause, then draws a clean chart with the measures. It works in the chat, and on the local whiteboard of this plugin (server board-control) when the person asks for it or agrees to it. Use when the user types /gr-whiteboard:five-whys, asks for a Five Whys (Nazenaze) analysis, or when consult-on-board or issue-driven picks it.
---
# five-whys
Ask why with the person, one step at a time, until each branch reaches its root cause. Use the person's words, not your own guesses.
Talk in the chat first, one why at a time in short bullets. Open the board only when the person asks for it, or when a picture would make it clearer and you ask "Shall we sort this out on the whiteboard?" and they agree; then run it as the skill `talk-on-board` says.
## Board
- After `open_board`, start the watch Monitor of `talk-on-board` (Open step 2, `client.js watch`) at once, or you miss every Send.
- From the top: the title (the framework name and the subject), the root cause definition from `SKILL_DIR/data/labels.json` in small gray text, then the chart (SKILL_DIR is the folder of this file).
- Answer as in a phone chat: `write_answer` puts your answer below and left of the person's last comment. When the person only wrote in the chart, put it under your previous answer instead (`at`).
- Draw the draft in the shape of `SKILL_DIR/data/chart-ja.mmd` for a Japanese speaker, or `SKILL_DIR/data/chart-en.mmd`, with the person's words: the problem on the left, the whys to the right, occurrence on top and outflow below, each first branch marked at its head. When a branch grows, add its boxes to the right.
## Checks
Check each answer as you go. When one fails, ask a short question; do not fix it yourself. When the subject is plain, add it yourself, and confirm such additions once, when a step settles.
- One box holds one sentence. Do not leave out the subject or the verb, nor the object of a transitive verb.
- One box holds one cause. When an answer has two causes, split the branch.
- The chain explains the specific part of the problem (where, when, which one), not only a general cause.
- When two conditions must both hold, write them as two boxes under the same why, not as a chain.
- The subject is a role (worker, designer), never a person's name.
- Each answer is a cause of the answer before it, not a measure.
- Do not skip a step.
- Do not stop at blaming a person. Ask what let the mistake happen.
- Occurrence (why it happened) and outflow (why it was not caught) are separate branches. Split other branches when needed.
- Five is not a rule. Stop at the root cause, sooner or later.
- Do not say the same thing twice in other words. Do not let the logic loop.
- A root cause is a cause that prevents the problem from coming back when it is removed, and that the team itself can act on with a concrete control or improvement.
## Clean chart
1. For each root cause, ask the person for a measure and settle it in one sentence. When the person has none, ask the people or files that know the facts, and offer candidates for an OK. When the person leaves it to you, fill it from those sources and mark the box as a proposal. Each measure removes its root cause and agrees with every why on its branch. Each measure comes from a root cause on the chart. For a measure with no root cause, add its branch first.
2. When all branches are done, ask "Shall I draw the clean chart?". Draw only after a yes.
3. Before drawing, read each branch both ways: from the problem down with "why?", and from the root cause up with "so". Each link holds both ways; where one does not, ask the person.
4. Draw it right of the draft with `draw_mermaid` in the shape of the template, one row per branch; keep the draft. Head each box with its step ("Why 1", "Why 2", and "Root cause" for the root cause), in the person's language. Write its own title and the gray definition above it.
5. Line up the root causes in one column and the measures in the next (`edit_items`).
6. Make the root cause boxes thick (`edit_items`, `strokeWidth` 4).
Pliki w paczce (4)
- SKILL.md 4 KB
- data/chart-en.mmd 1 KB
- data/chart-ja.mmd 1 KB
- data/labels.json 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · GoodRelax/gr-whiteboard | 90 | Apache-2.0 |
| kirodotdev/kirocrew | 100 | Apache-2.0 |
| pinkroosterai/PinkRoosterSkills | 100 | MIT |
| veevia/design-agency | 100 | MIT |
| ysskrishna/ai-agent-skills | 100 | MIT |
| wesammustafa/Claude-Code-Everything-You-Need-to-Know | 82 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 32bac99efea9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90issue-driven
Prowadzi od tła sprawy do jednego pytania wartego odpowiedzi, a dalej do wyzwań, miar i zadań, na czacie lub tablicy. - 100five-whys-root-cause
Stosuje konsultingową metodę pięciu pytań dlaczego, gdy problem wraca lub pierwsze wyjaśnienie jest zbyt płytkie, do ustrukturyzowanej diagnozy i planu działań. - 100consult-on-board
Prowadzi rozmowę doradczą z użyciem wielu ram biznesowych i przechodzi do lokalnej tablicy tylko wtedy, gdy użytkownik o nią poprosi. - 100022-root-cause-analysis
Prowadzi analizę przyczyn źródłowych metodami 5 Whys, Ishikawa i drzewa rzeczywistości, zanim zaproponuje poprawkę. - 90Five Whys Root Cause Analysis
Diagnozuje przyczyny źródłowe problemu metodą pięciu „dlaczego”, zwracając listę kandydatów uszeregowaną według prawdopodobieństwa, bez poprawek. - 100awesome-root-cause
Prowadzi analizę przyczyn źródłowych incydentów, powtarzających się awarii i problemów procesowych metodami 5 Whys, rybiej ości, PDCA i A3, na przykład do postmortem.