Toyota Kata
Apply Mike Rother's Toyota Kata from "Toyota Kata — Managing People for Improvement, Adaptiveness and Superior Results" (McGraw-Hill, 2009) — structured, scientific improvement routines. Covers the Improvement Kata (4 steps — understand the direction, grasp the current condition, establish the next target condition, iterate experiments toward the target) and the Coaching Kata (5 questions a coach asks the improver), the "threshold of knowledge" idea, PDCA inside the Improvement Kata, storyboards, the improver/coach/2nd-coach hierarchy, and why kata, not tools, are the advantage. Use when a tea
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill toyota-katagit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/toyota-kata ~/.claude/skills/toyota-kataPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Toyota Kata (Mike Rother) Apply this skill when continuous improvement has stalled, when retrospectives produce action items that don't change behavior, when a team has Kanban and metrics but no improvement engine, when leadership wants to grow the team's improvement capability instead of dictating solutions, or when applying the scientific method to process change without the overhead of a formal A3. ## Core Philosophy **Toyota's competitive advantage isn't TPS tools.** It's the *kata* — the daily routines of scientific experimentation and coaching that produce continuous improvement. Other companies copied the tools (kanban, andon, 5S) and got short-term gains; the kata is what produces the long-term adaptive capability. **Improvement is a skill, not an event.** It's developed by daily practice, not by quarterly initiatives or Kaizen events. **Two complementary kata.** The **Improvement Kata** is the routine the improver follows. The **Coaching Kata** is the routine the coach uses to develop the improver's capability. They work together: the coach asks structured questions that make the improver think scientifically. **Embrace the threshold of knowledge.** At any moment, you know some things and don't know others. The boundary is the threshold of knowledge. Improvement happens by designing experiments that push past it. **Move toward a target condition, not toward "better".** Vague aspirations don't drive learning. Specific, measurable target conditions do.
Details
- Skill name
toyota-kata- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/toyota-kata/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Toyota Kata skill do?
Apply Mike Rother's Toyota Kata from "Toyota Kata — Managing People for Improvement, Adaptiveness and Superior Results" (McGraw-Hill, 2009) — structured, scientific improvement routines. Covers the Improvement Kata (4 steps — understand the direction, grasp the current condition, establish the next target condition, iterate experiments toward the target) and the Coaching Kata (5 questions a coach asks the improver), the "threshold of knowledge" idea, PDCA inside the Improvement Kata, storyboards, the improver/coach/2nd-coach hierarchy, and why kata, not tools, are the advantage. Use when a tea
How do I install the Toyota Kata skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Toyota Kata popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Triz
5catch-the-wave/fullstack-ios-claude-skills
TRIZ systematic innovation methodology with AI-enhanced prompts. Use when: (1) Technical contradiction - improve A but B worsens, (2) Physical contradiction - need opposite properties, (3) Cross-industry solutions via FOS/MOS, (4) Technology evolution prediction, (5) Complex engineering problems. Triggers: "TRIZ", "contradiction", "inventive", "trade-off", "improve without worsening", "ข้อขัดแย้งทางเทคนิค", "innovation breakthrough
Software UX Research
8Freddy-CHEN-ux/00_claude_skills
UX research and analysis for discovering, validating, and evaluating software experiences, including research ops, governance, and measurement.
Triz Product Architect
5catch-the-wave/fullstack-ios-claude-skills
TRIZ-powered product architecture and design decisions. Use when facing product trade-offs ("more features vs simplicity"), choosing between design approaches, resolving UX contradictions, making architecture decisions, or when the user says "TRIZ", "trade-off", "contradiction", "can we have both", "approach A vs B", or asks you to evaluate competing design directions. NOT for generic engineering — this is for product craft.
Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.