with one click
kaizen
持续改进方法论 - 基于精益思想
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
持续改进方法论 - 基于精益思想
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
研究一个**已知的** GitHub 项目/repo,判断它对 LiYe Systems 的进化有没有可借鉴之处,产出定型的 evolution-recon 报告并归档到 recon-log。Use whenever the user gives a specific GitHub repo URL and asks to 研究/研读/消化/digest/study it, wants to know whether a project 对 LiYe / AGE / loamwise 有没有帮助/可借鉴/值得参考, asks "这个项目对我们有没有用", floats "看看 <repo> 有没有能学的", or types /github-digest — even if they never name the report format. This is the KNOWN-repo research step that sits UPSTREAM of github-scout (which DISCOVERS unknown repos) and source-intake (which INGESTS a chosen repo). Reach for it when the repo is already chosen and the real question is "is it worth our attention / what can LiYe learn". Do NOT use it to search/discover repos (that is github-scout) or to actually vendor/ingest a repo (that is source-intake).
Use when testing SFC v0.2 frontmatter compatibility.
Claude Skills 创建指南与最佳实践
SFC patched skill. Use when "ui-ux" is relevant.
内容研究与写作助手
视觉设计与艺术创作工具
| name | kaizen |
| description | 持续改进方法论 - 基于精益思想 |
| domain | 00_Core_Utilities |
| category | productivity |
| version | 1.0.0 |
| status | active |
| source | awesome-claude-skills |
| source_url | https://github.com/ComposioHQ/awesome-claude-skills |
| license | Apache-2.0 |
| skeleton | workflow |
| triggers | {"commands":["/kaizen"],"patterns":["kaizen"]} |
| inputs | {"required":[],"optional":[]} |
| outputs | {"artifacts":["SKILL.md"]} |
| failure_modes | [{"symptom":"Missing required inputs or context","recovery":"Provide the missing info and retry"},{"symptom":"Unexpected tool/runtime failure","recovery":"Rerun with minimal steps; escalate after 3 failures"}] |
| verification | {"evidence_required":true,"how_to_verify":["node .claude/scripts/sfc_lint.mjs <skill_dir>"]} |
| governance | {"constitution":"_meta/governance/SKILL_CONSTITUTION_v0.1.md","policy":"_meta/policies/DEFAULT_SKILL_POLICY.md"} |
来源: ComposioHQ/awesome-claude-skills 适配: LiYe OS 三层架构
应用持续改进方法论,基于日本改善哲学和精益方法论,提供多种分析方法。
当需要持续改进流程或系统时:
Plan (计划)
↓ 识别问题,制定假设
Do (执行)
↓ 小规模试验
Check (检查)
↓ 分析结果
Act (行动)
→ 标准化或调整
逐层追问"为什么",找到根本原因:
问题: 报表生成时间过长
Why 1: 数据查询慢 → 为什么?
Why 2: 表没有索引 → 为什么?
Why 3: 没有 DBA 评审 → 为什么?
Why 4: 缺少代码审查流程 → 为什么?
Why 5: 团队没有建立标准 ← 根本原因
| 浪费类型 | 含义 | 示例 |
|---|---|---|
| 过度生产 | 做得比需要多 | 过多的报表 |
| 等待 | 空闲时间 | 等待审批 |
| 运输 | 不必要的移动 | 多次文件传输 |
| 过度加工 | 过度精细 | 过度优化代码 |
| 库存 | 堆积的工作 | 待处理任务积压 |
| 动作 | 不必要的操作 | 重复手动操作 |
| 缺陷 | 返工 | Bug 修复 |
用户: 我的日报流程太繁琐了,帮我优化
Claude: [使用 kaizen 绘制价值流图、识别浪费、提出改进方案]
用户: 这个项目延期了,帮我分析原因
Claude: [使用 kaizen 5 Why 分析、找到根本原因、制定预防措施]
用户: 帮我建立一个持续改进的机制
Claude: [使用 kaizen 设计 PDCA 循环、定义检查点、建立反馈机制]
无外部依赖,纯方法论技能。
此技能被以下业务域引用:
Kaizen 理念与 LiYe OS 的 Evolution Protocol 高度一致:
Created: 2025-12-28 | Adapted for LiYe OS