kaizen-improvement-system
Skill31 starsChanged 18 days agoMITView on GitHub
Use when auditing or improving this engineering engine or a product it produces. Coordinates evidence-backed baselines, small experiments, standardisation, and re-audits without replacing domain skills.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- peterbamuhigire/business-plan-skillstheir own version, first seen Nov 15, 2026
- peterbamuhigire/proposal-skillstheir own version, first seen Oct 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- peterbamuhigire/proposal-skills★ 11same name
- peterbamuhigire/business-plan-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository172 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- 00-meta-initializationSkill
- chwezi-dev-engineSkill
- ai-agent-commercial-operationsSkill
- ai-agent-compliance-controlsSkill
- ai-agent-governance-and-limitsSkill
- ai-agent-multi-agent-coordinationSkill
- ai-agent-observability-evaluationSkill
- ai-agent-runtime-architectureSkill
- ai-agent-safety-and-red-teamSkill
- ai-agent-tooling-and-hitlSkill
- ai-analyticsSkill
- ai-app-architectureSkill
- ai-cost-and-meteringSkill
- ai-economic-value-engineSkill
- ai-evaluationSkill
- ai-feature-rollout-and-experimentationSkill
- ai-feature-specSkill
- ai-incident-responseSkill
- ai-llm-integrationSkill
- ai-model-gatewaySkill
- ai-observability-and-debuggingSkill
- ai-opportunity-canvasSkill
- ai-prompt-engineeringSkill
- ai-rag-patternsSkill
- ai-securitySkill
- ai-web-appsSkill
- coding-agent-optimizationSkill
- openai-agents-sdkSkill
- android-developmentSkill
- api-design-firstSkill
- distributed-systems-patternsSkill
- ecommerce-platform-audit-requirementsSkill
- graphql-patternsSkill
- microservices-architectureSkill
- system-architecture-designSkill
- validation-contractSkill
- database-design-engineeringSkill
- database-reliabilitySkill
- mysql-engineeringSkill
- postgresql-engineeringSkill
- cicd-pipelinesSkill
- cloud-architectureSkill
- deployment-release-engineeringSkill
- docker-developmentSkill
- infrastructure-as-codeSkill
- kubernetes-platformSkill
- observability-monitoringSkill
- reliability-engineeringSkill
- execution-plan-scriptsSkill
- accounting-engineSkill
- accounting-finance-controllerSkill
- electronic-fiscal-taxingSkill
- multicurrency-and-fxSkill
- avalonia-desktop-developmentSkill
- frontend-architectureSkill
- frontend-performanceSkill
- image-compressionSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use this skill to turn observed defects, incidents, feedback, source changes, or audit gaps into small, reversible, evidence-backed …
- Distinctive: line 49
Teach and re-measure: Update discoverability and handoffs, re-score the changed dimensions, and leave the next improvement visible.
- Distinctive: line 70
Do not award 70+ without extraordinary, specific proof or claim production readiness without executable or rendered evidence.
- Very specific: line 116
Every Kaizen cycle must begin with digital-research-engine source evaluation and source verification.
- Very specific: line 149
Read and search are required.
- Distinctive: line 156
If a validator, source, user result, render, system environment, or independent review is unavailable, keep the gap visible and state its …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kaizen Improvement System
Use this skill to turn observed defects, incidents, feedback, source changes, or audit gaps into small, reversible, evidence-backed improvements. It keeps domain judgement with the owning engine and makes learning discoverable.
<!-- dual-compat-start -->Use When
- Auditing or grading the engineering catalogue or a product made with it.
- Turning defects, incidents, user feedback, or new evidence into a tested improvement.
- Planning a major iteration, quarterly engine review, or post-release re-audit.
Do Not Use When
- A single-skill safety review is the only task; use the skill safety gate in
skill-engine-audit. - A current external claim is needed before source evaluation and verification.
- The proposed change is cosmetic and has no measurable effect on routing, quality, safety, or delivery.
Required Inputs
- Engine or product path, intended audience, output types, owner, and constraints.
- Current routes, references, tests, user or product evidence, and known failure modes.
- Baseline scoring method, improvement target, acceptance evidence, rollback condition, and re-audit date.
Prerequisites
- Read
docs/continuous-improvement/kaizen-adoption-2026-08.md. - For portfolio or current-standards claims, use the Digital Research engine's source-evaluation and source-verification routes.
Workflow
- Observe. Inspect the real route, output, users, constraints, evidence, and failure mode.
- Baseline. Inventory applicable dimensions and score them with named evidence. Keep raw scores, blockers, uncertainty, and
NOT ASSESSEDitems visible. Publish the repository policy cap ofmin(raw_score, 65)for permanent audits. - Select. Choose the smallest high-leverage root cause. Prefer repeated defects, user harm, safety issues, missing proof, and routing failures over added prose.
- Experiment. Name the exact skill, reference, fixture, validator, or gate; hypothesis; owner; measure; risk; rollback; stop condition; and re-audit date.
- Check. Re-run relevant validators, tests, source checks, user or product checks, and independent review. Preserve negative evidence.
- Standardise. Promote a successful result into the owning skill, reference, template, fixture, router, or release gate. Do not promote a one-off observation.
- Teach and re-measure. Update discoverability and handoffs, re-score the changed dimensions, and leave the next improvement visible.
At retrospective, ask which evidence, repository context, stakeholder access, runtime capability, or tool result was unavailable to the work. Separate process failure from missing access; improve the workflow only where a changed method can alter the outcome.
Core content
For a product, assess the applicable combination of requirements, architecture
or document correctness, security and privacy, accessibility, reliability,
performance, user value, deployment or handoff, rollback, and evidence quality.
For an engine, assess doctrine, taxonomy and routing, skill depth, applied
proof, standards currency, output readiness, hygiene, safety, and integrity. For
client-facing web or dashboard work, also load
references/purpose-fit-premium-ux-implementation.md and require an implementation
slice that preserves the client's design thesis rather than copying a reference product.
Quality Standards
- Scores cite concrete evidence and a one-line deficiency statement.
- A target of 95/100 is an improvement target, not an achievement claim.
- Do not award 70+ without extraordinary, specific proof or claim production readiness without executable or rendered evidence.
- Structural, behavioural, render, system, and production evidence are labelled separately.
- Missing execution, source, approval, or artefact evidence is
NOT ASSESSED. - A safety, legal, financial, privacy, security, or release blocker remains a blocker regardless of score.
- Lessons are stored only when repeatable, generalisable, significant, actionable, and likely to prevent recurrence.
Anti-Patterns
- Adding a skill without a demonstrated routing or ownership gap. Fix: inventory and test the collision first.
- Awarding a high score because headings or checkboxes exist. Fix: require outcome-level evidence.
- Treating a green unit or structural test as product proof. Fix: add the smallest relevant behavioural, failure, render, or handoff check.
- Closing an action because prose changed. Fix: close only when named acceptance evidence exists and a fresh agent can find the result.
- Hiding an unavailable check inside an overall score. Fix: mark it
NOT ASSESSEDwith an owner and date. - Keeping every retrospective note forever. Fix: promote durable learning and remove redundant narrative.
- Treating a polished screenshot as a premium implementation. Fix: test real content, critical states, responsive reflow, keyboard/focus, reduced motion, performance, and recovery.
- Copying a recognisable competitor surface. Fix: implement the user principle and the client's visual thesis, then retain a rationale and originality review.
Outputs
| Artifact | Consumed by | Template |
| Capped scorecard and evidence register | Maintainer and reviewer | Kaizen adoption plan and local report |
| Improvement action record | Owner and implementer | Gap, root cause, change, hypothesis, measure, risk, rollback, evidence |
| Standardisation record | Future agents and router | Skill, reference, fixture, validator, or gate change |
| Re-audit handoff | Next reviewer | Date, owner, remaining gaps, and required checks |
Evidence Produced
| Category | Artifact | Format | Example |
| Correctness | Baseline and re-score | Markdown table | Raw dimensions, cap, blockers, and evidence |
| Security | Safety and integrity review | Markdown | Permission, provenance, and harmful-output findings |
| Operability | Rollback and re-audit handoff | Markdown | Owner, stop condition, recovery, and next date |
| Release evidence | Validator and test record | Command output or Markdown | Positive, negative, and unavailable checks |
Read next
skill-engine-auditfor the engine rubric and evidence matrix.skill-engine-auditsafety gate for changed or imported skill safety review.advanced-testing-strategyfor risk-scaled validation.world-class-engineeringfor delivery gates and operational handoff.
Mandatory Digital Research currentness gate
Every Kaizen cycle must begin with digital-research-engine source evaluation
and source verification. Record scope, dates, freshness class, support status,
uncertainty, and review date for current standards, APIs, frameworks, packages,
security, platform, and lifecycle claims; quarantine unsupported claims as
NOT_ASSESSED. Apply the currentness gate at
digital-research-engine/docs/continuous-improvement/kaizen-currentness-gate.md
(resolve that engine per device).
Include claims using superlatives such as “largest”, “first”, “only”, “most severe”, and emergency severity scores in the currentness preflight. Verify severity and scores against the issuing authority; support historical comparisons with a defined comparison set and dated evidence. If either is missing, narrow the claim and record it as unsupported instead of repeating it.
References
docs/continuous-improvement/kaizen-adoption-2026-08.md- local adoption plan.digital-research-engine/docs/continuous-improvement/portfolio-kaizen-standard-2026-08.md(resolve that engine per device) - cross-engine standard.skills/sdlc-meta/skill-engine-audit/- audit dimensions, scoring, and report structure.skills/sdlc-meta/skill-engine-audit/references/skill-safety-gate.md- safety and source-ingestion gate.skills/sdlc-meta/kaizen-improvement-system/references/purpose-fit-premium-ux-implementation.md- implementation patterns for friction reduction, dashboards, state feedback, and authored visual systems.
<!-- dual-compat-end -->Inputs
| Artefact | Produced by | Required? | Why |
| Engine or product path and output types | Router or task owner | yes | Fixes the audit boundary |
| Current evidence and failure history | Validators, tests, users, or operators | yes | Prevents opinion-only scoring |
| Target and constraints | Task owner | yes | Defines the experiment and rollback |
Capability contract
Read and search are required. Execution is preferred for validators and tests;
editing requires an authorised improvement scope. Without execution, report the
exact checks as NOT ASSESSED. Network research is optional and must use
source-disciplined routes.
Degraded mode
If a validator, source, user result, render, system environment, or independent review is unavailable, keep the gap visible and state its consequence. Return a conditional plan or verdict; never convert unavailable evidence into a pass.
Decision rules
| Condition | Action | Failure avoided |
| A repeated defect has a clear owning skill or gate | Patch that source of truth and add a focused regression check | Symptom-only fixes and recurrence |
| The proposed change adds only prose or a duplicate route | Do not change the catalogue; record the gap or route to the existing owner | Kaizen bloat and routing noise |
| The result changes a cross-engine handoff | Require source owner, receiving owner, artefacts, uncertainty contract, and fallback | Silent ownership drift |
| A material outcome, render, system, or production check cannot run | Mark it NOT ASSESSED and retain the blocker | False readiness |
| The experiment passes its acceptance evidence | Standardise the result and schedule re-measurement | Learning lost in a one-off patch |
The book-wave operating contract is book-driven system decision and agent orchestration. Current technology and security claims must pass Digital Research verification.
The 2026-09-02 cross-engine study is Book-driven Kaizen Wave 3; use it for currentness-gated contracts, testing, Git recovery, secure input handling, protocol semantics, and agent evaluation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

