From rad-brainstormer
5 whys, root cause analysis, why does this keep happening, find the root cause, trace this problem. Dig beneath surface symptoms to find the real problem. Toyota production system methodology.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rad-brainstormer:five-whys [problem or symptom to trace][problem or symptom to trace]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply the 5 Whys root cause analysis to: **$ARGUMENTS**
Apply the 5 Whys root cause analysis to: $ARGUMENTS
Originally from Toyota's production system, adapted here for brainstorming. The goal is to ensure the RIGHT problem is being solved before generating solutions.
Start with the stated problem, then ask "Why?" repeatedly:
Problem: [stated problem] "Why does this happen?" / "Why is this a problem?"
Why 1: [user's answer] "And why does THAT happen?"
Why 2: [user's answer] "And why is that the case?"
Why 3: [user's answer] "What causes that?"
Why 4: [user's answer] "And what's behind that?"
Why 5: [user's answer — likely close to root cause]
Present: "Now that [root cause] has been identified as the core issue, this is what to brainstorm solutions for — not the original symptom of [stated problem]. Proceed to brainstorm solutions for this root cause?"
If yes, recommend the appropriate brainstorming technique based on the root cause nature. Consult references/methodology-catalog.md for technique selection guidance.
npx claudepluginhub radorigin-llc/rad-claude-skills --plugin rad-brainstormerProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.