kaizen
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseKaizen
Kaizen
来源: ComposioHQ/awesome-claude-skills 适配: LiYe OS 三层架构
应用持续改进方法论,基于日本改善哲学和精益方法论,提供多种分析方法。
Source: ComposioHQ/awesome-claude-skills Adapted for: LiYe OS Three-Tier Architecture
Apply continuous improvement methodology based on Japanese Kaizen philosophy and lean methodology, with multiple analytical methods available.
When to Use This Skill
When to Use This Skill
当需要持续改进流程或系统时:
- 分析现有流程找出改进点
- 应用 PDCA 循环迭代改进
- 使用 5 Why 追溯根本原因
- 识别和消除浪费 (Muda)
- 制定渐进式改进计划
When continuous improvement of processes or systems is needed:
- Analyze existing processes to identify improvement points
- Apply PDCA cycle for iterative improvement
- Use 5 Why to trace root causes
- Identify and eliminate waste (Muda)
- Develop incremental improvement plans
Core Capabilities
Core Capabilities
1. PDCA 循环
1. PDCA Cycle
Plan (计划)
↓ 识别问题,制定假设
Do (执行)
↓ 小规模试验
Check (检查)
↓ 分析结果
Act (行动)
→ 标准化或调整Plan (Plan)
↓ Identify problems and develop hypotheses
Do (Do)
↓ Conduct small-scale trials
Check (Check)
↓ Analyze results
Act (Act)
→ Standardize or adjust2. 5 Why 分析
2. 5 Why Analysis
逐层追问"为什么",找到根本原因:
问题: 报表生成时间过长
Why 1: 数据查询慢 → 为什么?
Why 2: 表没有索引 → 为什么?
Why 3: 没有 DBA 评审 → 为什么?
Why 4: 缺少代码审查流程 → 为什么?
Why 5: 团队没有建立标准 ← 根本原因Ask "why" layer by layer to find the root cause:
Problem: Report generation takes too long
Why 1: Slow data query → Why?
Why 2: No index on the table → Why?
Why 3: No DBA review → Why?
Why 4: Lack of code review process → Why?
Why 5: No established team standards ← Root cause3. 价值流图 (Value Stream Mapping)
3. Value Stream Mapping
- 绘制当前状态流程
- 识别增值 vs 非增值活动
- 设计未来状态
- 制定转变计划
- Map current-state processes
- Identify value-added vs non-value-added activities
- Design future-state processes
- Develop transition plans
4. 浪费识别 (7 Muda)
4. Waste Identification (7 Muda)
| 浪费类型 | 含义 | 示例 |
|---|---|---|
| 过度生产 | 做得比需要多 | 过多的报表 |
| 等待 | 空闲时间 | 等待审批 |
| 运输 | 不必要的移动 | 多次文件传输 |
| 过度加工 | 过度精细 | 过度优化代码 |
| 库存 | 堆积的工作 | 待处理任务积压 |
| 动作 | 不必要的操作 | 重复手动操作 |
| 缺陷 | 返工 | Bug 修复 |
| Waste Type | Definition | Example |
|---|---|---|
| Overproduction | Produce more than needed | Excessive reports |
| Waiting | Idle time | Waiting for approval |
| Transportation | Unnecessary movement | Multiple file transfers |
| Overprocessing | Overly refined | Over-optimizing code |
| Inventory | Piled-up work | Backlog of pending tasks |
| Motion | Unnecessary operations | Repetitive manual tasks |
| Defects | Rework | Bug fixes |
5. 渐进式改进计划
5. Incremental Improvement Plan
- 小步快跑
- 每次只改一件事
- 快速验证
- 持续迭代
- Move forward in small steps
- Change only one thing at a time
- Validate quickly
- Iterate continuously
Usage Examples
Usage Examples
示例 1: 优化工作流程
Example 1: Optimize Workflow
用户: 我的日报流程太繁琐了,帮我优化
Claude: [使用 kaizen 绘制价值流图、识别浪费、提出改进方案]User: My daily report process is too tedious, help me optimize it
Claude: [Uses kaizen to map value stream, identify waste, and propose improvement solutions]示例 2: 复盘失败项目
Example 2: Retrospect a Failed Project
用户: 这个项目延期了,帮我分析原因
Claude: [使用 kaizen 5 Why 分析、找到根本原因、制定预防措施]User: This project was delayed, help me analyze the reasons
Claude: [Uses kaizen 5 Why analysis to find root causes and develop preventive measures]示例 3: 建立改进循环
Example 3: Establish an Improvement Cycle
用户: 帮我建立一个持续改进的机制
Claude: [使用 kaizen 设计 PDCA 循环、定义检查点、建立反馈机制]User: Help me set up a continuous improvement mechanism
Claude: [Uses kaizen to design PDCA cycle, define checkpoints, and establish feedback mechanisms]Dependencies
Dependencies
无外部依赖,纯方法论技能。
No external dependencies; this is a pure methodology skill.
LiYe OS Integration
LiYe OS Integration
业务域引用
Business Domain References
此技能被以下业务域引用:
- 12_Meta_Cognition: 持续改进方法论(主域)
- 11_Life_Design: 生活流程优化
This skill is referenced by the following business domains:
- 12_Meta_Cognition: Continuous Improvement Methodology (Primary Domain)
- 11_Life_Design: Life Process Optimization
与 Evolution Protocol 的关系
Relationship with Evolution Protocol
Kaizen 理念与 LiYe OS 的 Evolution Protocol 高度一致:
- 都强调持续改进
- 都基于数据驱动决策
- 都要求可追溯的记录
The Kaizen concept is highly aligned with LiYe OS's Evolution Protocol:
- Both emphasize continuous improvement
- Both are based on data-driven decision-making
- Both require traceable records
三层架构位置
Position in Three-Tier Architecture
- 物理层 (本文件): Skills/00_Core_Utilities/productivity/kaizen/
- 逻辑层索引: Skills/{domain}/index.yaml
- L3 指令层: .claude/skills/{domain}/kaizen/
Created: 2025-12-28 | Adapted for LiYe OS
- Physical Layer (This file): Skills/00_Core_Utilities/productivity/kaizen/
- Logical Layer Index: Skills/{domain}/index.yaml
- L3 Instruction Layer: .claude/skills/{domain}/kaizen/
Created: 2025-12-28 | Adapted for LiYe OS