kaizen:cause-and-effect

Identify and prioritize root causes using a six-category fishbone framework.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dalawwa/labor-methods --skill kaizen-cause-and-effect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen:cause-and-effect
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/kaizen/skills/cause-and-effect
Command: npx skills add https://github.com/dalawwa/labor-methods --skill kaizen-cause-and-effect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Fishbone (Ishikawa) analysis framework helps teams systematically identify, categorize, and prioritize root causes behind a problem across six categories, enabling targeted improvements.

Core Features & Use Cases

  • Structured six-category cause analysis (People, Process, Technology, Environment, Methods, Materials)
  • Root-cause identification with "why" technique and prioritization
  • Actionable solutions and mitigation steps for high-impact causes
  • Use Case: When a problem is not obvious, generate a fishbone diagram to surface contributing factors and drive focused interventions.

Quick Start

Provide a problem description and run a fishbone analysis to identify and prioritize root causes.

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 analysis and when do I need to use it for root cause analysis?

A fishbone analysis systematically identifies and categorizes root causes across six categories: People, Process, Technology, Environment, Methods, and Materials. Use root cause analysis when a problem is not obvious and you need to surface contributing factors to drive focused interventions.

How do I identify root causes using the Ishikawa diagram method?

To identify root causes using the Ishikawa diagram method, map contributing factors across six categories, then apply iterative 'why' questioning to differentiate true root causes from contributing factors and rank them by impact and likelihood to yield prioritized solutions.

How do I prioritize root causes and generate an actionable plan from a fishbone diagram?

Prioritize root causes from a fishbone diagram by ranking identified factors based on impact and likelihood, which yields prioritized solutions. This process outputs a concise, actionable plan executable by a cross-functional team, including concrete remedies and steps to validate results.

Can I use this root cause analysis framework for continuous improvement in my team?

You can use this root cause analysis framework for continuous improvement because it applies the Kaizen philosophy to systematically map, categorize, and prioritize causes, enabling targeted improvements and cross-functional team execution of validated mitigation steps.

What's the best way to map out contributing factors when a problem is not obvious?

The best way to map contributing factors when a problem is not obvious is generating a fishbone diagram across six structured categories. This surfaces contributing factors, applies iterative 'why' questioning, and drives focused interventions to resolve complex underlying issues.

Does fishbone analysis work for problems involving technology and process categories simultaneously?

Fishbone analysis works for problems involving technology and process categories simultaneously by structuring the investigation across six distinct categories including Technology, Process, Methods, Materials, People, and Environment to ensure comprehensive root cause identification.