Apply Lean Manufacturing principles to software development for systematic problem-solving.
npx skills add https://github.com/freitasp1/claude-code-skills --skill kaizen-freitasp1
Please help me install this Agent Skill. Skill: kaizen Source: https://github.com/freitasp1/claude-code-skills/tree/main/skills/kaizen Command: npx skills add https://github.com/freitasp1/claude-code-skills --skill kaizen-freitasp1
This Skill integrates Lean Manufacturing principles like 5 Whys, Ishikawa diagrams, and PDCA cycles into software development workflows to systematically solve problems and improve code quality.
/why) to drill down to the fundamental cause of issues, ideal for bug analysis and production incidents./cause-and-effect), useful for debugging intricate bugs./plan-do-check-act), ensuring measurable improvements.Initiate a root cause analysis for a production incident by typing /why followed by a description of the problem.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for a production incidents is performed using the 5 Whys method to drill down iteratively until the fundamental cause is identified. This systematic approach prevents treating symptoms instead of the actual underlying defect.
Mapping complex debugging issues visually is done using Ishikawa diagrams, also known as fishbone diagrams. They map potential causes of intricate bugs across categories to visualize relationships and identify structural defects within the codebase.
Applying the PDCA cycle to iterative software development involves planning feature implementation, executing the work, checking measurable improvements, and acting on results. This ensures continuous improvement and structured refactoring cycles.
Integrating Lean manufacturing principles into a CI/CD pipeline enforces quality gates using Poka-Yoke error-proofing and YAGNI Just-In-Time principles. This prevents defects and reduces waste directly within continuous integration workflows.
Use 5 Whys for drilling down into a specific bug or production incidents to find a single root cause. Use Ishikawa diagrams for complex problems requiring visualization of multiple potential causes and their effects on code quality.
tcfialhoAnalyze incident files to construct causal chains and identify root causes.
JoturesGuide incremental code refactoring and process optimization using Kaizen principles.
garethdaineRun Laravel Pint, PHPStan, and PHPUnit code quality checks.
AcurioustractorAutomate sprint planning, standups, and health checks across ACT projects.