Kaizen: Continuous Improvement
Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.
When to Use
- Always applied for:*
- Code implementation and refactoring
- Architecture and design decisions
- Process and workflow improvements
- Error handling and validation
- Philosophy:* Quality through incremental progress and prevention, not perfection through massive effort.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
- Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Overview
- The Four Pillars
- Continuous Improvement (Kaizen)
- Poka-Yoke (Error Proofing)
- Standardized Work
- Just-In-Time (JIT)
- Integration with Commands
- Red Flags
- Remember
Reference Map
references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
1---2name: kaizen3description: Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.4license: MIT5---67# Kaizen: Continuous Improvement89Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.1011## When to Use12- *Always applied for:**13- Code implementation and refactoring14- Architecture and design decisions15- Process and workflow improvements16- Error handling and validation17- *Philosophy:** Quality through incremental progress and prevention, not perfection through massive effort.1819## Core Workflow201. Confirm the request matches this skill's trigger, scope, and risk profile.212. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.223. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.234. Apply only the relevant guidance instead of loading or repeating the entire reference by default.245. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.2526## Topic Map27- Overview28- The Four Pillars29- Continuous Improvement (Kaizen)30- Poka-Yoke (Error Proofing)31- Standardized Work32- Just-In-Time (JIT)33- Integration with Commands34- Red Flags35- Remember3637## Reference Map38- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.3940## Limitations41- Use this skill only when the task clearly matches the scope described above.42- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.43- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.4445## Progressive Loading46Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
newmindsgroup