Continuous Improvement

Implements PDCA cycles to analyze Vetinari episode_memory and prioritize operational improvements.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill continuous-improvement-strategicmilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Continuous Improvement
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/worker/continuous-improvement
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill continuous-improvement-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continuous Improvement automates the Plan-Do-Check-Act cycle to find recurring failure modes, prioritize high-value changes, and measure their real-world impact so the Vetinari orchestration system becomes more reliable, cost-efficient, and predictable over time.

Core Features & Use Cases

  • Data-driven diagnosis: Collects episode_memory, quality scores, cost and duration metrics to detect patterns and root causes.
  • Prioritization and planning: Ranks improvement opportunities by impact, effort, and risk and produces concrete change proposals with rollback plans.
  • Measurement and governance: Defines baselines, targets, measurement periods, and statistical significance criteria, then assesses outcomes and standardizes successful changes.
  • Use Case: Run a weekly improvement cycle to reduce Inspector rejection rates by identifying common defect categories, proposing targeted pre-submission checks, and measuring post-change impact.

Quick Start

Run a PDCA improvement review for the past 30 days of episode_memory to propose prioritized changes for reducing Inspector rejection rates.

Frequently Asked Questions about Continuous Improvement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a PDCA cycle to reduce recurring operational failures?

A PDCA cycle reduces recurring operational failures by analyzing historical execution data to detect failure patterns, drafting prioritized change proposals with rollback plans, and measuring post-change impact.

What is root-cause analysis used for in continuous improvement workflows?

Root-cause analysis in continuous improvement identifies the underlying reasons for recurring failure modes by collecting episode memory, quality scores, and cost metrics to detect systemic patterns.

How do I prioritize operational fixes using impact, effort, and risk metrics?

Prioritize operational fixes by ranking improvement opportunities based on calculated expected impact, implementation effort, and associated risk to produce structured, high-value change proposals.

How do I measure the statistical significance of reliability improvements?

Measure reliability improvements by defining baselines, setting targets, establishing measurement periods, and applying statistical significance criteria to assess outcomes and standardize successful changes.

Do I need historical execution data to run a kaizen improvement cycle?

Yes, running a kaizen improvement cycle requires access to historical execution data, including episode memory and quality metrics, to diagnose failures and calculate expected impact accurately.

What is the best way to propose changes that improve system reliability and cost?

The best way to propose reliability and cost improvements is automating the Plan-Do-Check-Act cycle to find recurring failure modes, prioritize high-value changes, and measure their real-world impact.