Slash Command

/kaizen-event

From cps-ops

Plan and facilitate a 3-5 day kaizen / improvement event.

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/cps-ops:kaizen-event

Model invocable

No pre-commands

Tool Access

This command is limited to the following tools:

ReadWriteEditGlobGrepBash

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /cps-ops:kaizen-event

**Kaizen Event Plan.** Plan and facilitate a 3-5 day kaizen / improvement event.

## When to use

When the engagement scope explicitly calls for kaizen event plan work in the operational excellence domain. Look for keywords like: lean, six sigma, VSM, kaizen, DMAIC.

## Inputs you should gather first

- The engagement `project.json` (industry, service line, regulatory frameworks)
- Relevant client documents already ingested into the brain (run `/cps:graph-query` to find them)
- Any prior CPS Operational Excellence deliverables for cross-reference (central brain)

##...

Command Content

42 lines · ~447 tokens

Stats

LanguageJavaScript

Parent stars0

MaintenanceGood

Last CommitMay 11, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

/cps-ops:kaizen-event

Kaizen Event Plan. Plan and facilitate a 3-5 day kaizen / improvement event.

When to use

When the engagement scope explicitly calls for kaizen event plan work in the operational excellence domain. Look for keywords like: lean, six sigma, VSM, kaizen, DMAIC.

Inputs you should gather first

The engagement project.json (industry, service line, regulatory frameworks)
Relevant client documents already ingested into the brain (run /cps:graph-query to find them)
Any prior CPS Operational Excellence deliverables for cross-reference (central brain)

Steps

Read the engagement project.json and confirm scope includes Operational Excellence.
Load the ops skill (plugins/ops/skills/ops/SKILL.md) and any matching industry skill.
Use the relevant subagent(s) — see Integration table below — to do the analysis.
Apply the methodology described in the skill, citing all sources.
Place the deliverable in 05_Deliverables_Final/ per the CPS file-location standard. Filename pattern: ops-kaizen-event-<client>-<YYYYMMDD>.md.
Run /cps:verify-quality before marking the workstream complete.

Output shape

A CPS-branded deliverable with:

Pyramid-Principle structure (recommendation up front)
Source citations on every data point
Recommendation Format used in any advice section
Quality bar items below all checked

Quality bar

VSM has explicit start/end nodes, takt time, cycle time per step, and value-added ratio
Process redesign quantifies before/after on cycle time, cost, defect rate
Kaizen events have a chartered scope, daily standup cadence, and Day 5 readout