kaizen

Diagnose targets, challenge blind spots, and implement prioritized improvements.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ntholm86/autonomous-agent-skills --skill kaizen-ntholm86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/ntholm86/autonomous-agent-skills/tree/main/archive/v2/kaizen
Command: npx skills add https://github.com/ntholm86/autonomous-agent-skills --skill kaizen-ntholm86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Facilitates incremental enhancements by diagnosing issues, challenging assumptions, and implementing targeted improvements efficiently.

Core Features & Use Cases

  • Diagnosis: Identifies strengths and weaknesses within a target, using lenses like unevenness, overburden, and waste to uncover root causes.
  • Blind Spot Challenge: Asks probing questions to uncover unseen risks, assumptions, or patterns overlooked during initial examination.
  • Prioritization and Implementation: Ranks findings by impact and applies the most effective changes, verifying improvements through testing.
  • Use Case: A software engineer uses this Skill to optimize a code module by methodically diagnosing inefficiencies, challenging assumptions, and iteratively refining the codebase.

Quick Start

Use the kaizen skill to analyze and improve a target by first diagnosing its current state, then challenging potential blind spots, and finally applying prioritized changes with verification.

Frequently Asked Questions about kaizen

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

FAQPage Schema
How do I identify root causes for code inefficiencies during optimization?

Root cause analysis for code inefficiencies uses diagnostic lenses like unevenness, overburden, and waste to uncover underlying issues. This structured approach methodically examines the target's current state to reveal specific process or system weaknesses before targeting improvements.

What is the best way to challenge blind spots when refining a software system?

Challenging blind spots during software refinement involves asking probing questions to uncover unseen risks, assumptions, or overlooked patterns. This diagnostic step ensures hidden vulnerabilities are exposed before prioritizing and implementing any targeted improvements.

How do I prioritize system improvements after diagnosing performance issues?

Prioritizing system improvements requires ranking diagnostic findings by their overall impact and applying the most effective changes first. This structured approach ensures iterative refinement targets high-value optimizations while verifying improvements through subsequent testing.

Can I use continuous improvement techniques for both code and process optimization?

Continuous improvement techniques support both code and process optimization tasks requiring detailed analysis and iterative refinement. The approach accommodates incremental enhancements across various targets by diagnosing issues, challenging assumptions, and implementing targeted improvements efficiently.

When should I use an iterative refinement approach for diagnosing system weaknesses?

Iterative refinement is suited for system optimization when you need to challenge assumptions and apply targeted improvements efficiently. It supports continuous development cycles where diagnosing current states and verifying incremental changes are required.

How does kaizen drive continuous improvement through diagnostics and iteration?

Kaizen drives continuous improvement by providing a structured approach for incremental enhancement of targets through diagnosis, blind spot testing, prioritization, and implementation, supporting continuous development cycles across process and code optimization tasks.