Skip to content

charlieviettq/awesome-agent-skill / .claude/skills/biz-lean-six-sigma

"biz-lean-six-sigma"

Verified

"Apply Lean and Six Sigma principles to eliminate waste and reduce process variation. Use this skill when the user needs to improve operational efficiency, identify the seven wastes (TIMWOOD), run DMAIC improvement projects, or streamline workflows — even if they say 'our process is too slow', 'where are we wasting resources', or 'how do we reduce defects'.".

FileKindSize
SKILL.mdskill md5.0 KB
examples/sample_scenario.mdmarkdown5.9 KB
references/spc-basics.mdmarkdown9.9 KB
references/value-stream-mapping.mdmarkdown12.3 KB

examples/sample_scenario.md

View on GitHub
# Example: 電商倉儲出貨流程改善

## Scenario

TaiStyle 是台灣一家中型服飾電商,日均出貨量約 800 筆。近期客訴大幅上升,主要抱怨「出貨太慢」和「收到錯誤商品」。營運主管 Jessica 整理了以下數據:

- 平均訂單處理時間:4.2 小時(客戶期望:2 小時內)
- 出貨錯誤率:8.3%(行業標竿:< 1%)
- 退換貨率因此升至 6.1%,每月損失約 NT$420,000
- 倉儲人員:12 人,三班制,常態性加班

Jessica 問:「我們哪裡在浪費資源?要從哪裡開始改?」

---

## Analysis

### Step 1:現況 Value Stream 盤點

訂單流程(依序):
1. 系統接單 → 2. 客服審核(人工)→ 3. 列印揀貨單 → 4. 揀貨員走去列印區取單 → 5. 走至倉位揀貨 → 6. 移至包裝區 → 7. 包裝 → 8. 貼標 → 9. 等待集貨區堆滿 → 10. 主管簽核後交貨運公司

觀察後發現:揀貨員平均每單步行 **380 公尺**,列印區到倉位平均 **120 公尺**;集貨區等到滿才放行,平均等待 **55 分鐘**。

---

### Step 2:TIMWOOD 廢棄物辨識

| Waste Type | Found? | Description | Impact |
|-----------|--------|-------------|--------|
| Transportation | **Y** | 貨品從備貨倉移至出貨倉,兩棟建築相距 80 公尺,每日搬運 15-20 次 | H |
| Inventory | **Y** | 熱銷款備料 45 天,但補貨週期僅需 7 天,多餘庫存佔用資金 NT$2.1M | M |
| Motion | **Y** | 揀貨員每單步行 380 公尺,取單需另走 120 公尺至列印區 | H |
| Waiting | **Y** | 集貨區等待滿載才放行,平均 55 分鐘;客服審核等待平均 28 分鐘 | H |
| Over-production | Y | 每日列印紙本揀貨單 900+ 張,其中約 8% 因訂單異動重印 | L |
| Over-processing | **Y** | 每筆訂單需客服人工審核;95% 訂單無任何異常,審核形同例行蓋章 | M |
| Defects | **Y** | 出貨錯誤率 8.3%,主因:紙本揀貨單字體小、品項代碼相似(S/M 碼) | H |

**最高衝擊廢棄物**:Motion(步行距離)、Waiting(集貨放行)、Defects(錯誤率)

---

### Step 3:Root Cause Analysis — 錯誤率 8.3%(5 Whys)

**問題**:出貨錯誤率 8.3%

1. **Why 1**:為什麼會發錯商品?
   → 揀貨員拿錯尺碼(S/M/L 碼混淆)

2. **Why 2**:為什麼會混淆尺碼?
   → 紙本揀貨單字體 8pt,倉位光線不足,不易辨識

3. **Why 3**:為什麼還在用紙本揀貨單?
   → 系統沒有行動端,倉庫沒有 WiFi 覆蓋

4. **Why 4**:為什麼沒有建置行動端?
   → 過去日均出貨量僅 200 筆,紙本夠用;業務成長後未重新評估工具

5. **Why 5**:為什麼業務成長後未重新評估?
   → **缺乏定期流程審查機制,無人負責主動提出改善需求**

**根本原因**:倉儲工具和流程未隨業務規模同步升級,且缺乏流程改善的責任制度。

---

### Step 4:DMAIC 改善計畫

| Phase | Action | Owner | Timeline |
|-------|--------|-------|----------|
| Define | 確立問題:出貨錯誤率從 8.3% 降至 1.5%;訂單處理時間從 4.2h 降至 1.8h | Jessica | Week 1 |
| Measure | 每日記錄錯誤類型(尺碼錯/商品錯/地址錯),建立缺陷分類基線 | 倉儲主管 | Week 1-2 |
| Analyze | Pareto 分析:確認 80% 錯誤集中在「尺碼混淆」(已驗證,佔 71%) | 品保 | Week 2 |
| Improve | (1)導入 WMS 行動揀貨系統 + 掃碼驗證;(2)取消集貨等滿制,改為每 15 分鐘定時放行;(3)低風險訂單系統自動審核,客服只處理異常旗標 | IT + 倉儲 | Week 3-6 |
| Control | 每日自動產生錯誤率報表;設定 SPC 管制線(UCL = 2%);每月流程審查會議 | Jessica | Week 7+ |

---

## Result

```markdown
# Lean Six Sigma Analysis: TaiStyle 倉儲出貨流程

## Current State
- Process: 電商訂單揀貨→包裝→出貨
- Key metric: 出貨錯誤率 / 訂單處理時間
- Current performance: 錯誤率 8.3%,處理時間 4.2 小時,每月損失 NT$420,000

## Waste Identification (TIMWOOD)
| Waste Type | Found? | Description | Impact |
|-----------|--------|-------------|--------|
| Transportation | Y | 兩棟建築跨倉移貨,每日 15-20 次 | H |
| Inventory | Y | 熱銷款備料 45 天,超過補貨週期 6.4 倍 | M |
| Motion | Y | 每單步行 380m,另需走 120m 取紙本揀貨單 | H |
| Waiting | Y | 集貨等滿 55 分鐘 + 客服審核 28 分鐘 | H |
| Over-production | Y | 每日重印揀貨單 72 張(8% 異動率) | L |
| Over-processing | Y | 95% 正常訂單仍需人工審核 | M |
| Defects | Y | 8.3% 錯誤率,主因尺碼混淆 | H |

## Root Cause Analysis
紙本揀貨單(字體小 + 光線不足)→ 尺碼混淆 → 出貨錯誤
根本原因:倉儲工具未隨業務成長升級,缺乏流程改善責任制度

## Improvement Plan (DMAIC)
| Phase | Action | Owner | Timeline |
|-------|--------|-------|----------|
| Define | 設定目標:錯誤率 ≤1.5%,處理時間 ≤1.8h | Jessica | Week 1 |
| Measure | 建立每日錯誤類型分類基線 | 倉儲主管 | Week 1-2 |
| Analyze | Pareto 確認 71% 錯誤為尺碼混淆 | 品保 | Week 2 |
| Improve | WMS 行動揀貨 + 掃碼驗證;定時放行;自動審核低風險訂單 | IT + 倉儲 | Week 3-6 |
| Control | 每日錯誤率報表 + SPC 管制線(UCL=2%);月度流程審查 | Jessica | Week 7+ |

## Expected Impact
- 出貨錯誤率:8.3% → 1.5%(↓82%)
- 訂單處理時間:4.2h → 1.8h(↓57%)
- 每月損失:NT$420,000 → 估計 NT$75,000(↓82%)
- 揀貨員步行距離:380m/單 → 估計 220m/單(取消跑印表機)
```

> **注意**:導入 WMS 需前期投資(估計 NT$180,000 建置費),回收期約 **0.4 個月**(以每月節省 NT$345,000 計算)。Jessica 應優先推動「定時放行」和「自動審核」兩項零成本改善,同步進行 WMS 採購評估,不需等到系統上線才開始降低等待廢棄物。
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall