Toyota Way
Apply Jeffrey Liker's "The Toyota Way — 14 Management Principles from the World's Greatest Manufacturer" (2004; 2nd ed. 2021), the management system behind the Toyota Production System. Covers the 4P model (philosophy, process, people and partners, problem solving) and the 14 principles, the TPS house (just-in-time and jidoka on heijunka, standardised work and kaizen), the wastes (muda, mura, muri, unused creativity) mapped to software, and Toyota product development (chief engineer, set-based design, front-loading). Includes a review mode that scores a process, ways-of-working or governance d
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-waygit 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-way ~/.claude/skills/toyota-wayPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# The Toyota Way (Jeffrey Liker) Apply this skill when someone is designing or reviewing *how work is managed*: a delivery process, a ways-of-working document, an improvement programme, a governance model. It is the management-system lens behind the tools. `kanban`, `flow-efficiency` and `toyota-kata` cover specific mechanisms; this skill asks whether the system around them is built to surface problems, develop people and keep improving. ## Core Philosophy **The tools are not the system.** Many companies copied kanban cards, andon cords and 5S, and few got Toyota's results. Liker's argument is that the tools work only inside a management philosophy: long-term thinking, flow that exposes problems, people who are developed to solve them, and leaders who go and see. Adopting the tools without the philosophy produces *lean as a toolbox*, which fades once the consultants leave. **Two pillars (the internal "Toyota Way 2001").** *Continuous improvement*: challenge, kaizen and genchi genbutsu. *Respect for people*: respect and teamwork. Respect here means expecting people to think, and giving them the means to improve their own work. It does not mean being nice. **Make problems visible, then solve them at the root.** Flow, pull and stopping to fix problems are designed to surface problems quickly. A system that hides problems in inventory, buffers or status reports can't improve. Lowering the water reveals the rocks.
Details
- Skill name
toyota-way- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/toyota-way/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Toyota Way skill do?
Apply Jeffrey Liker's "The Toyota Way — 14 Management Principles from the World's Greatest Manufacturer" (2004; 2nd ed. 2021), the management system behind the Toyota Production System. Covers the 4P model (philosophy, process, people and partners, problem solving) and the 14 principles, the TPS house (just-in-time and jidoka on heijunka, standardised work and kaizen), the wastes (muda, mura, muri, unused creativity) mapped to software, and Toyota product development (chief engineer, set-based design, front-loading). Includes a review mode that scores a process, ways-of-working or governance d
How do I install the Toyota Way 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 Way 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.
Two Axis Code Review
5vnovakovits/claude-skills
Review a branch or pull request on two separate axes, reported side by side and never merged into one ranking. Standards — does the diff follow this repository's written rules (CLAUDE.md, AGENTS.md, CONTRIBUTING, coding standards) plus a baseline of Fowler's code smells? Spec — does it do what the ticket, spec or plan asked, with nothing missing, nothing extra and nothing done wrongly? Draws on Boehm's verification vs validation ("building the product right" vs "building the right product"), Google's code-review practice and Matt Pocock's two-axis review. Covers pinning the diff to a merge bas
Tidy First
5vnovakovits/claude-skills
Apply Kent Beck's "Tidy First?" approach — small structure changes (tidyings) separated from behavior changes, sequenced as "first / after / later / never", informed by software design as an economic activity (coupling, cohesion, optionality, discount rate). Use when about to make a behavior change in messy code, when reviewing a tangled PR, when deciding whether to clean up now or later, or when thinking about software design as a long-running investment decision rather than a craft aesthetic.
User Segmentation
8Freddy-CHEN-ux/00_claude_skills
Framework for clustering users into behavioral segments and personas. Use when analyzing user cohorts, identifying patterns, and personalizing product features.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.