Kaizen Refinement

Kaizen Skill Refinement

Overview

This skill operationalizes the philosophy of Kaizen (Continuous Improvement). It ensures that after each coding session, existing agent skills are evaluated, refined, and permanently improved to eliminate waste (Muda) and standardize success.

Core Principles

1. PDCA (Plan-Do-Check-Act)

• Plan: Identify an inefficiency or friction point from the recent session (e.g., repeating the same mistake, missing architectural context).
• Do: Formulate a specific, small modification to the relevant SKILL.md file.
• Check: Verify that the proposed modification is clear, concise, and complies with the targeted skill's operational context.
• Act: Apply the change to the SKILL.md file using file editing tools to standardize the new process.

2. Root Cause Analysis (The 5 Whys)

• Before adding raw instructions to a skill, ask "Why" the friction occurred until the systemic root cause is identified. Fix the root cause in the skill's instructions, rather than treating the symptom.

3. Standardization

• Improvements are only valid if they are codified. Always update the SKILL.md of the relevant skill directly to ensure the agent uses the new standard in future sessions.

Execution Steps for the Agent

When triggered to perform a Kaizen refinement: 1. Review Recent Activity: Analyze the most recent coding session for errors, user corrections, context drops, or unnecessarily repetitive tool usage. 2. Identify Target Skill: Determine which existing skill (e.g., ui-development, mac-os-integration) maps to the domain where the friction occurred. 3. Draft the Improvement: Write an update that strictly follows the AgentSkills.io SKILL.md specification. Keep instructions atomic and actionable. 4. Update the Skill: Execute the file modification to inject the improvement into the target SKILL.md. 5. Report: Briefly notify the user of the optimization made.

Edge Cases

• No Friction Found: If the session operated perfectly, review existing skills for outdated information or bloat, and perform a minor simplification (eliminating waste).
• Missing Domain Skill: If the friction relates to a new domain entirely, propose the creation of a new, fully compliant <name>/SKILL.md directory cluster rather than polluting an unrelated skill.