kaizen

Apply Kaizen continuous improvement methodology to analyze processes and eliminate waste.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/dev-khoi/AURA-conHack-2026 --skill kaizen-dev-khoi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/dev-khoi/AURA-conHack-2026/tree/main/.opencode/skills/kaizen
Command: npx skills add https://github.com/dev-khoi/AURA-conHack-2026 --skill kaizen-dev-khoi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Processes accumulate inefficiencies, bottlenecks, and waste over time, and teams often lack a structured method to identify root causes and implement low-risk incremental improvements. ## Core Features & Use Cases - Waste Identification: Systematically detect the 7 types of waste (TIMWOOD) in any workflow using Gemba observation and value stream mapping. - PDCA Improvement Cycles: Structure Plan-Do-Check-Act iterations to test small changes before standardizing them. - Kaizen Event Planning: Run focused 2-5 day improvement workshops with charters, milestones, and measurable goals. - Use Case: A software team with 6-week feature delivery uses this Skill to map their current state, identify waiting waste between design and development, and implement parallel workflows that cut delivery time by 60%. ## Quick Start Use the kaizen skill to analyze our invoice approval process and identify waste causing the 30-day processing delay.

Frequently Asked Questions about kaizen

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

FAQPage Schema
How do I run a Kaizen event for process improvement?▼

A Kaizen event is a focused 2-5 day workshop with 5-10 people targeting a specific process. Day 1 maps the current state, days 2-3 analyze root causes and design solutions, and days 4-5 implement quick wins and document new standard work.

What are the 7 types of waste in Kaizen?▼

The 7 wastes are Transport, Inventory, Motion, Waiting, Overproduction, Overprocessing, and Defects, remembered with the acronym TIMWOOD. Identifying these wastes in each process step is the core of Kaizen analysis.

How does the PDCA cycle work in continuous improvement?▼

PDCA stands for Plan, Do, Check, Act. You plan a change based on data, implement it on a small scale, measure results against expectations, then standardize the change if successful or iterate with a new plan.

What is the difference between Kaizen and traditional improvement?▼

Kaizen uses small, low-risk incremental changes involving everyone continuously, while traditional improvement relies on large, top-down, project-based changes. Kaizen focuses on process improvement rather than just outcome targets.

When should I not use Kaizen for process improvement?▼

Avoid Kaizen when you skip Gemba observation, attempt big-bang changes, or lack baseline metrics to measure improvement. It also fails as a one-time event since waste returns without continuous follow-up and standardization.