kaizen

Name: kaizen
Availability: InStock
Author: kennyolofsson23-netizen

Identify root causes and produce prioritized countermeasures with Five Whys and PDCA cycles.

1|Updated Mar 15, 2026

Search Tags:#kaizen #root-cause-analysis #five-whys #continuous-improvement #fishbone #pdca #a3

Ready to run

npx skills add https://github.com/kennyolofsson23-netizen/claude-code-config --skill kaizen-kennyolofsson23-netizen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/kennyolofsson23-netizen/claude-code-config/tree/main/skills/kaizen
Command: npx skills add https://github.com/kennyolofsson23-netizen/claude-code-config --skill kaizen-kennyolofsson23-netizen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and eliminate recurring defects, process waste, and design or implementation inefficiencies by finding root causes and guiding small, verifiable improvements that prevent recurrence and improve quality over time.

Core Features & Use Cases

Root Cause Analysis: Structured Five Whys investigations that move from symptoms to systemic causes.
Multi‑method Analysis: Fishbone (cause-and-effect), A3 one-page problem reports, PDCA cycles, Gemba Walks, Value Stream Mapping, and Muda (waste) analysis for different contexts.
Practical Outcomes: Produces prioritized countermeasures, implementation plans, and monitoring steps so teams can apply fixes incrementally and measure impact.
Use Case: Run a Fishbone + Five Whys on a flaky checkout flow to discover process, technology, and people causes, then produce an A3 with a PDCA plan to reduce incidents.

Quick Start

Analyze "API returns 500 error on checkout" with Five Whys and provide prioritized countermeasures and a PDCA-style next step.

Frequently Asked Questions about kaizen

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

FAQPage Schema

How do I perform a root cause analysis for a flaky software checkout flow?▼

To perform root cause analysis for a flaky checkout flow, you apply structured methods like Five Whys and Fishbone diagrams to trace symptoms to systemic causes. This produces prioritized countermeasures to prevent recurrence.

What is the best way to document a post-incident investigation for an API returning 500 errors?▼

The best way to document a post-incident investigation for an API returning 500 errors is creating an A3 one-page problem report. It captures the root cause analysis and outlines a PDCA cycle for incremental improvements.

How do I identify and eliminate process waste in team workflows?▼

To identify and eliminate process waste in team workflows, you conduct Muda analysis and Value Stream Mapping. These techniques pinpoint inefficiencies and guide small, verifiable improvements that enhance quality over time.

Can I use Five Whys and Fishbone analysis for software architecture decisions?▼

Yes, you can use Five Whys and Fishbone analysis for software architecture decisions. They structure the evaluation of design inefficiencies, helping you trace implementation flaws and produce targeted architectural countermeasures.

When should I use a PDCA cycle instead of a standard root cause trace?▼

You should use a PDCA cycle instead of a standard root cause trace when you need to implement, verify, and monitor incremental fixes over time. It provides a structured plan to measure the impact of applied countermeasures continuously.