Monozukuri: Use a Japanese Craftsmanship Workflow to Get Your Agent Writing Clean, Verifiable Code

Who this is for

• Developers who want their agent to follow an auditable process when writing code (Observe → Understand → Plan → Craft → Verify → Reflect → Improve) rather than dumping code in one shot.
• Users of agents that support the Agent Skills format: each skill is a top-level <name>/SKILL.md directory, and official documentation states it is compatible with any agent supporting that format. Invoke explicitly via $monozukuri-core.
• When it is NOT a fit: the evidence does not state the specific runtime versions it depends on, does not list verified client compatibility, and does not address support for text/documentation tasks — this skill targets software building and maintenance; do not assume other uses unless the evidence covers them.
• Not stated officially: supported programming languages, whether network access is required, and the specific side-effect boundaries of each skill — no evidence exists for any of these; confirm before use.

Your first attempt in 3 minutes

Prerequisites: Node.js/npx installed locally; an agent that supports the Agent Skills format. The official docs offer two installation methods; only one main path is recommended here:

Main path: install the core skill via the skills CLI

Run in your project root:

npx skills add kuya-egg/Monozukuri --skill monozukuri-core

This installs only the umbrella skill monozukuri-core. If you later want all 12 skills (the umbrella skill + 11 focused skills), the same official CLI supports wildcards:

npx skills add kuya-egg/Monozukuri --skill '*'

(The official docs also offer installation as a Claude Code plugin: run /plugin marketplace add kuya-egg/Monozukuri, then /plugin install monozukuri@monozukuri; this installs all 12 skills under the monozukuri namespace. This is not treated as a parallel main path here.)

Trigger a low-risk task: once installed, explicitly type $monozukuri-core in your agent and give it a small read-only/analysis task, e.g. "follow the craftsmanship process to check the correctness and simplicity of a small function". The core workflow is Observe → Understand → Plan → Craft → Verify → Reflect → Kaizen.

Success signals: the agent structures its answer around the seven phases above instead of throwing code at you directly; and when focused skills are chained in the official order (nemawashi → genchi-genbutsu → kanso → kata → poka-yoke → kodawari → andon → shukka), all skills are in effect. Note: this skill targets code tasks; there are no separate rubrics for fiction/professional documents. If you give it a text-writing task, the evidence does not guarantee a corresponding process. $monozukuri-core is only the explicit trigger; whether it reads/writes files, executes commands, or accesses the network is not stated officially — pick a side-effect-free task for your first attempt.

Use cases

Case 1: craftsmanship-style review of a small function Scenario: you want the agent to seriously examine an existing piece of code. How to start: type $monozukuri-core in a supported agent, attach the target code, and ask for a process-based evaluation. Workflow used: the umbrella skill's Observe → Understand → Plan → Craft → Verify → Reflect → Kaizen. Expected outcome: the agent provides observations, understanding, plan, and verification suggestions phase by phase, rather than rewriting directly; whether it waits for your confirmation before touching files is not stated in the evidence — it is advisable to explicitly request analysis-only, no file changes.

Case 2: full feature development via the focused-skill chain Scenario: first install all skills (--skill '*' or the Claude Code plugin route), then have the agent develop a small feature. Workflow used: the focused skills chained in the official order nemawashi → genchi-genbutsu → kanso → kata → poka-yoke → kodawari → andon → shukka, covering the full path from preparation to verification. Expected outcome: the agent advances through each skill's phases and delivers the output of each phase; the individual trigger conditions and specific side effects of each focused skill are not detailed in the evidence — before actual execution, ask the agent to confirm whether each step will modify code.

Usage boundaries

• Installation differs by platform: the skills CLI (npx skills add ...) is the universal path; on Claude Code use /plugin marketplace add + /plugin install monozukuri@monozukuri, which installs all 12 skills under the monozukuri namespace. Do not mix the two or infer installation methods for other clients.
• Trigger method: officially documented as explicit invocation of $monozukuri-core; the invocation syntax for other skills is not given in the evidence.
• Side effects and confirmation points: this skill guides the agent to write code, but the evidence does not state whether it directly modifies your files, executes commands, or accesses the network; all of these are unknown. For a first attempt, prefer read-only analysis tasks, and ask the agent to show its plan before making any changes.
• Officially stated limitations: installing monozukuri-core alone includes only the umbrella-skill workflow; the full skill chain requires installing all 12 skills. The official docs do not provide supported programming languages, locale requirements, network requirements, or a client compatibility list.
• Unverified key information: the specific behavior of each focused skill, update/uninstall procedures, and any terms of use beyond the license are not covered by the evidence — check the original repository before use.