kaizen-cause-and-effect

Analyze root causes using the Fishbone diagram across six predefined categories.

Updated Mar 10, 2026

Search Tags:#problem solving #root cause analysis #process improvement #kaizen #ishikawa #fishbone diagram

Ready to run

npx skills add https://github.com/Gamezar/opencode-cek --skill kaizen-cause-and-effect-gamezar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kaizen-cause-and-effect
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/kaizen/skills/kaizen-cause-and-effect
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill kaizen-cause-and-effect-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically identify the root causes of a problem by exploring potential contributing factors across multiple categories, preventing superficial solutions.

Core Features & Use Cases

Systematic Cause Analysis: Utilizes the Fishbone (Ishikawa) diagram methodology.
Categorized Brainstorming: Explores causes across People, Process, Technology, Environment, Methods, and Materials.
Deep Dive Questioning: Encourages asking "why" to uncover underlying issues.
Use Case: A software team is experiencing frequent production bugs. This Skill can be used to analyze the problem, exploring how team knowledge, development processes, tooling, deployment environment, coding practices, and external dependencies might be contributing to the bugs.

Quick Start

Analyze the problem 'API response latency is too high' using the cause and effect skill.

Frequently Asked Questions about kaizen-cause-and-effect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a fishbone diagram and how does it help with root cause analysis?▼

A fishbone diagram systematically explores potential causes across six categories—People, Process, Technology, Environment, Methods, and Materials—to uncover systemic root causes rather than applying superficial fixes to a stated problem.

How do I conduct root cause analysis for production bugs?▼

To conduct root cause analysis for production bugs, you systematically brainstorm and deep-dive questioning across six predefined categories to identify how team knowledge, processes, tooling, and coding practices contribute to the errors.

Can I use the Ishikawa diagram methodology to analyze API response latency?▼

Yes, you can use the Ishikawa diagram methodology to analyze API response latency by exploring contributing factors like process inefficiencies, technology limitations, and environmental constraints to pinpoint systemic issues.

What's the best way to structure a cause and effect brainstorming session?▼

The best way to structure a cause and effect brainstorming session is using a Fishbone diagram methodology, exploring potential causes across six categories while asking deep-dive "why" questions to uncover underlying issues.

When should I use fishbone diagram root cause analysis instead of other problem solving methods?▼

You should use fishbone diagram root cause analysis when a problem involves multiple contributing factors and you need structured, categorized brainstorming across areas like Process, Technology, and Methods to prevent superficial solutions.

What are the limitations of using the Ishikawa diagram for process improvement?▼

The limitations of using the Ishikawa diagram include relying entirely on the six predefined categories (People, Process, Technology, Environment, Methods, Materials), which may constrain brainstorming if a problem involves external factors outside these dimensions.