kaizen

Reviews autonomy run history and publishes evidence-backed process improvement tasks for maintainers.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill kaizen-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kaizen
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/profiles/simple-gh/skills/kaizen
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill kaizen-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous agent workflows accumulate failures, rework, and misleading measurements that no one systematically reviews. This Skill closes that loop by auditing normalized session history and durable outcomes, then filing evidence-backed improvement tasks so process problems get fixed instead of repeating. ## Core Features & Use Cases - Run History Review: Discovers and loads agent sessions through a normalized history interface, reconciling transcript claims against task state, git history, PR checks, and what actually landed. - Evidence-Based Findings: Publishes findings only when supported by multiple occurrences or one severe case, with causal mechanisms, counterevidence, and testable acceptance criteria. - Governed Publishing: Writes dated audit reports under docs/audits and files inputRequired tasks under docs/plans on an isolated branch, without ever modifying governance, roadmap, or merging work. - Use Case: After a month of autonomous runs, invoke this Skill to detect recurring verification failures, produce a Kaizen report, and open a PR proposing maintainer decisions with measurable acceptance criteria. ## Quick Start Ask the agent to run a Kaizen review of the last 30 days of autonomy sessions and publish a report with any findings as inputRequired tasks.

Frequently Asked Questions about kaizen

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

FAQPage Schema
How do I review autonomous agent run history for process failures?▼

Run a Kaizen review that discovers sessions through a normalized history interface, reconciles transcript claims with git history and PR checks, and publishes findings only when supported by multiple occurrences or one severe case with clear impact.

What evidence is required before filing a process improvement task?▼

A finding needs at least two independent occurrences or one severe occurrence, a causal process mechanism, corroborating session and durable outcome evidence, counterevidence, a maintainer decision, and observable acceptance criteria.

Can Kaizen create product roadmap tasks or merge changes?▼

No. Kaizen never creates roadmap work, implements, dispatches, or merges anything. It files inputRequired tasks requesting a Maintainer decision and publishes reports through an ordinary reviewed proposal PR.

What review window does the audit use on first run?▼

The first run uses a 30-day window. Subsequent runs cover sessions since the newest merged Kaizen report, and every fourth ISO week adds a 90-day longitudinal review of recurrence after prior decisions.

What happens when session history cannot be loaded for a harness?▼

The gap is recorded as an observability limitation and claims are restricted to durable outcomes that can be inspected directly. Private native JSONL or SQLite formats are never silently parsed as a substitute.