skills.rest
fockus
fockusCOMMUNITY
Explore all skills by this author →
GitHub

kaizen:cause-and-effect

Map root causes across six Fishbone categories to identify prioritized solutions.

2|Updated Mar 30, 2026
Search Tags:#analysis#problem-solving#root-cause#kaizen#process-improvement#fishbone#ishikawa
One-click install
npx skills add https://github.com/fockus/claude-skill-build --skill kaizen-cause-and-effect-fockus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kaizen:cause-and-effect
Source: https://github.com/fockus/claude-skill-build/tree/main/skills/kaizen-cause-and-effect
Command: npx skills add https://github.com/fockus/claude-skill-build --skill kaizen-cause-and-effect-fockus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Fishbone (Ishikawa) analysis to map potential causes across standard categories and reveal root issues.

Core Features & Use Cases

  • Structured multi-category cause analysis across People, Process, Technology, Environment, Methods, and Materials.
  • Prioritization and root-cause identification with actionable solutions.
  • Use Case: for a manufacturing outage or process defect, map causes and identify top contributing factors.

Quick Start

Provide a clear problem statement to initiate a fishbone analysis and generate categorized causes.

Frequently Asked Questions about kaizen:cause-and-effect

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

FAQPage Schema
How do I conduct a fishbone analysis for a manufacturing process defect?▼

Ishikawa analysis maps root causes of process defects across six categories: People, Process, Technology, Environment, Methods, and Materials. You provide a clear problem statement to generate categorized causes and identify top contributing factors for prioritized solutions.

What is the best way to identify root causes of recurring incidents in product development?▼

Root-cause identification for product development incidents uses structured Fishbone analysis to map causes across standard categories and reveal root issues. This approach helps prioritize actionable solutions and guides Kaizen initiatives for process improvement.

Can I use this Ishikawa diagram approach for performance issues in operations?▼

Yes, Ishikawa diagram analysis applies to problem-solving scenarios in operations, product development, and process improvement, including incidents, defects, and performance issues. It maps root causes across six categories to identify prioritized solutions.

How do I start a root-cause analysis when I only have a vague problem statement?▼

To start root-cause analysis, provide a clear problem statement to initiate the fishbone analysis. The skill then generates categorized causes across People, Process, Technology, Environment, Methods, and Materials to help identify top contributing factors.

Does fishbone analysis work for mapping causes of a manufacturing outage?▼

Fishbone analysis works for a manufacturing outage by mapping causes across six standard categories and identifying top contributing factors. It systematically reveals root issues and generates prioritized, actionable solutions to guide Kaizen initiatives.

Related Skills

Explore More Data & Analytics Skills→
qa-amanqa-aman
19

root-cause-analysis

Apply 5 Whys and fishbone mapping to document root-cause countermeasures.

Community
Advanced
scruffydanscruffydan

five-whys

Guide teams through five whys analysis to identify root causes and solutions.

Community
Basic
matdev83matdev83

golang-observability

Implement logging, metrics, tracing, and alerting for Go applications.

Community
Advanced
jsagirjsagir
2

root-cause

Guide Root Cause Analysis using 5-Whys, Fishbone, and Fault Tree methods.

Community
Intermediate