kaizen

Identify small, atomic code improvements with documented rationale and impact.

1|1|Updated Dec 28, 2025

Search Tags:#kaizen #entropy #code-cleanup #continuous-improvement #process-refinement #waste-elimination

Ready to run

npx skills add https://github.com/ssimhan/meal-planner --skill kaizen-ssimhan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/ssimhan/meal-planner/tree/main/skills/kaizen
Command: npx skills add https://github.com/ssimhan/meal-planner --skill kaizen-ssimhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kaizen provides a structured approach to continuous, incremental improvement of codebases and development processes, ensuring sessions end with tangible quality gains rather than merely finishing.

Core Features & Use Cases

Incremental improvements: Identify small, atomic changes that reduce complexity, improve readability, or remove dead code.
Standardization and cleanliness: Align naming conventions and UI patterns to reduce entropy across related files.
Documentation and traceability: Record the rationale and impact of each improvement for future iterations and audits.
Usage Context: Trigger during /closeout or between development iterations to continuously refine the system.

Quick Start

Trigger Kaizen during /closeout to identify one small improvement to make before finalizing.

Frequently Asked Questions about kaizen

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

FAQPage Schema

How do I apply continuous improvement to an existing codebase without causing regressions?▼

Code cleanup during closeout involves identifying one small, low-risk improvement to apply before finalizing. You document the rationale and impact of each atomic change to ensure traceability and tangible quality gains.

What is the best way to track the rationale behind incremental code refactoring?▼

Tracking rationale for incremental refactoring requires documenting the reason and impact of each change. This creates an auditable trail for future iterations and ensures that every atomic modification yields a repeatable gain.

How do I reduce code entropy across related files during ongoing development?▼

Reducing code entropy is achieved by standardizing naming conventions and aligning UI patterns across related files. This structured incremental process removes waste and ensures development sessions end with tangible quality improvements.

Can I use a lightweight checklist for post-mortem code reviews?▼

Yes, a lightweight checklist is used to guide post-mortem code reviews and identify actionable improvements. It ensures changes remain atomic, low-risk, and fully traceable to their documented impact.

When should I not use incremental changes for codebase maintenance?▼

Incremental changes are not suitable when a development session requires large, sweeping architectural overhauls rather than atomic, low-risk modifications. This approach specifically targets small, actionable improvements and waste elimination.