lean-improve

Designs and implements Lean improvements including Kaizen events, 5S, Kanban, SMED, and To-Be value stream maps.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill lean-improve-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-improve
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/lean-improve
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill lean-improve-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Teams often jump to implementing Lean tools without validated root causes, or run Kaizen events without charters, metrics, or documented standards, so improvements fade within weeks. This Skill structures the Improve phase of the Lean cycle so changes target confirmed root causes and produce measurable, sustainable results. ## Core Features & Use Cases - To-Be VSM Design: Build the future-state value stream map from the As-Is map using Takt Time, pull systems, continuous flow, and pacemaker principles, with an As-Is vs To-Be metrics comparison table. - Kaizen Event Execution: Run structured 2-5 day improvement events with defined roles, a day-by-day plan, and a charter template covering objectives, metrics, scope, and results. - Tool Selection by Waste Type: Map each dominant TIMWOOD waste to the right Lean tool (5S, Kanban, SMED, Jidoka, Heijunka, NVA elimination) with a detailed tools reference guide. - Use Case: After a Lean analysis confirms that waiting waste dominates invoice approval (68% of lead time), use this Skill to design a Kanban-based pull system, run a 5-day Kaizen event, and document Standard Work with a 5S audit checklist. ## Quick Start Ask the agent to design the To-Be value stream map and plan a Kaizen event for the validated root causes from your completed Lean analysis.

Frequently Asked Questions about lean-improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Kaizen event for process improvement?▼

A Kaizen event runs 2-5 days with a structured plan: Day 1 aligns the team on the charter and root causes, Day 2 measures the current state, Day 3 implements improvements, Day 4 tests and adjusts with metrics, and Day 5 documents Standard Work and presents results to the sponsor.

Which Lean tool should I use for each type of waste?▼

Match the tool to the dominant waste: 5S for motion and searching, Kanban for overproduction and inventory, SMED for waiting caused by setup times, Jidoka and poka-yoke for defects, and NVA elimination for overprocessing. The skill includes a full waste-to-tool mapping table.

When should I not start the Lean Improve phase?▼

Do not start Improve without a completed root cause analysis from the Analyze phase, without Process Owner authorization, or when causes point to statistical variation requiring DMAIC tools like SPC or MSA instead of Lean flow tools.

How do I calculate WIP limits for a Kanban system?▼

Use Little's Law: WIP equals throughput multiplied by target lead time. Alternatively, observe current WIP, reduce it by 20 percent, and measure the impact on lead time. Limits that are constantly violated signal a bottleneck upstream.

Why do Lean improvements fail after a Kaizen event?▼

Improvements regress when Standard Work is not documented, results are not measured against baseline metrics, or 5S is treated as cosmetic rather than tied to a root cause. Without documented standards, processes typically revert within 2-4 weeks.