kaizen

Implement one measured incremental change at a time across code, architecture, and workflows.

2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/ShunmeiCho/dotclaude --skill kaizen-shunmeicho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/ShunmeiCho/dotclaude/tree/main/skills/kaizen
Command: npx skills add https://github.com/ShunmeiCho/dotclaude --skill kaizen-shunmeicho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kaizen provides a structured approach to continuous improvement in code, architecture, and processes, helping teams avoid over-engineering by guiding small, incremental changes that improve quality over time.

Core Features & Use Cases

  • Incremental improvement: implement small changes that cumulatively boost reliability and maintainability.
  • Error-proof design: embed validations and guardrails to prevent regressions and design flaws.
  • Pattern-driven development: follow established patterns, document decisions, and reduce rewrites.
  • Refactoring guidance: plan, execute, and review refactors with measurable outcomes.

Quick Start

Start with a single, well-scoped improvement in your current project, implement the smallest viable change, run tests, and commit with a clear rationale.

Frequently Asked Questions about kaizen

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

FAQPage Schema
How do I plan and execute code refactoring without introducing regressions?

Continuous improvement uses incremental changes to boost reliability and maintainability. You implement one small, measured change at a time across tasks like validation and error handling, validating each step to ensure cumulative quality improvements without over-engineering.

What is the best way to apply continuous improvement to existing architecture?

Continuous improvement uses incremental changes to boost reliability and maintainability. You implement one small, measured change at a time across tasks like validation and error handling, validating each step to ensure cumulative quality improvements without over-engineering.

How do I start with pattern-driven development for incremental code changes?

Pattern-driven development starts by scoping a single improvement in your project. You implement the smallest viable change, adhere to established patterns, document decisions, run tests, and commit with a clear rationale to reduce future rewrites.

Does continuous improvement work for optimizing development workflows?

Continuous improvement applies directly to process optimization and development workflows. It guides small, iterative changes to your processes, embedding validations and guardrails to prevent design flaws and improve overall workflow reliability over time.

What is the difference between incremental changes and large-scale refactoring?

Incremental changes focus on small, iterative improvements validated at each step, whereas large-scale refactoring risks over-engineering. This approach enforces one measured change at a time, adhering to established patterns and documentation standards to ensure measurable outcomes.

When should I not use small iterative improvements for code quality?

Avoid small iterative improvements when a complete rewrite is mandated or established patterns are absent. This approach relies on adhering to existing patterns and documentation standards, making it unsuitable for unstructured codebases lacking measurable validation steps.