kaizen

Identify MUDA, MURA, and MURI signals and generate a prioritized improvement backlog.

7|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AndurilCode/craftwork --skill kaizen-andurilcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/AndurilCode/craftwork/tree/main/plugins/craftwork-professional/skills/kaizen
Command: npx skills add https://github.com/AndurilCode/craftwork --skill kaizen-andurilcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kaizen helps you continuously improve a codebase by identifying waste, unevenness, and overburden at the code level, then producing small, actionable changes that compound into better code health.

Core Features & Use Cases

  • Continuous improvement audit: Runs a structured scan across seven dimensions to produce an improvement map.
  • Targeted focus without tunnel vision: Accepts a focus description to prioritize what matters most while still scanning the whole codebase for critical issues.
  • Actionable backlog and PDCA plan: Synthesizes findings into a capped, prioritized improvement backlog plus a PLAN/DO/CHECK/ACT roadmap.
  • Best for incremental refactoring: Works well when you want “cleaner, healthier, safer code” without a full rewrite and not as a PR-style diff review.

Quick Start

Run the kaizen audit on your repository by telling the AI: run the kaizen skill to identify the smallest high-impact improvements to make this codebase healthier.

Frequently Asked Questions about kaizen

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

FAQPage Schema
How do I identify and prioritize technical debt for incremental refactoring?

Targeted codebase audits scan the entire project while applying your focus description to prioritize relevant technical debt, ensuring critical issues are still surfaced without restricting the analysis scope to specific directories.

What is the best way to plan continuous improvement for codebase health?

Continuous improvement planning uses a structured seven-dimension workflow to audit code health, producing evidence-based findings and a PLAN/DO/CHECK/ACT roadmap that converts systematic issues into single-PR-scope incremental changes.

How does a codebase audit convert technical debt into actionable changes?

A codebase audit converts technical debt into actionable changes by evaluating MUDA, MURA, and MURI signals, generating evidence-based findings, and capping them into a prioritized backlog with single-PR-scope guidance for follow-through.

Should I use incremental cleanup instead of a full codebase rewrite?

Incremental cleanup is ideal when you want healthier, safer code without a full rewrite, applying small compounding changes via a prioritized backlog rather than performing a PR-style diff review.