toyota-kata

Apply Toyota Kata improvement and coaching routines to drive daily scientific process experimentation.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/vnovakovits/claude-skills --skill toyota-kata-vnovakovits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: toyota-kata
Source: https://github.com/vnovakovits/claude-skills/tree/main/plugins/engineering-practices/skills/toyota-kata
Command: npx skills add https://github.com/vnovakovits/claude-skills --skill toyota-kata-vnovakovits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often adopt Kanban boards, metrics, and retrospectives yet see continuous improvement stall, with action items that never change behavior. This Skill provides Mike Rother's Toyota Kata framework — the Improvement Kata and Coaching Kata — to turn improvement into a daily, coached, scientific practice rather than an empty ritual. ## Core Features & Use Cases - Improvement Kata (4 Steps): Understand the direction, grasp the current condition with measurable data, establish a specific time-bounded target condition, and iterate small PDCA experiments toward it. - Coaching Kata (5 Questions): A structured daily coaching routine that develops the improver's capability by asking questions instead of providing answers, supported by storyboards and a three-level improver/coach/2nd-coach hierarchy. - Use Case: A team with highly variable cycle time (p50=4d, p95=19d) sets a 4-week target of p85 ≤ 5 days, then runs daily predicted experiments — such as rotating review duty — to systematically remove obstacles like slow first reviews. ## Quick Start Ask Claude to help you set up a Toyota Kata improvement cycle for your team's stalled cycle-time problem, including a target condition and the first experiment.

Frequently Asked Questions about toyota-kata

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

FAQPage Schema
How do I apply Toyota Kata to a software team?▼

Start by grasping your current condition with measurable data like cycle time percentiles, then set a specific time-bounded target condition outside current knowledge. Run small daily PDCA experiments with written predictions, coached through the five questions.

What are the 5 Coaching Kata questions?▼

The five questions are: What is the target condition? What is the actual condition now? What obstacles prevent reaching the target and which are you addressing? What is your next step and what do you expect? When can we go see what we learned?

Toyota Kata vs retrospectives: which is better for continuous improvement?▼

Toyota Kata runs daily with structured coaching, while retrospectives run every iteration and produce action items without experimentation follow-through. They combine well: retrospectives surface obstacles and kata works on them daily.

Why do Toyota Kata experiments need a written prediction?▼

Without a prediction, you cannot tell whether an experiment confirmed or surprised your expectation, so the learning value is lost. The prediction makes each PDCA cycle a real hypothesis test rather than just trying things.

When should a team not use Toyota Kata?▼

Avoid it when you cannot commit to a daily or near-daily coaching cadence, when targets are just known action items rather than genuine unknowns, or when leadership insists on dictating solutions instead of developing the team's improvement capability.