kaizen-reflect

Automate post-work reflections to extract impediments, root causes, and improvements.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen-reflect
Source: https://github.com/Garsson-io/kaizen/tree/main/.agents/skills/kaizen-reflect
Command: npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recursive Kaizen patterns often stall after a project completes, leaving missed improvements and unclear next steps. kaizen-reflect automates the post-work reflection, extracting impediments, root causes, and actionable improvements to feed the backlog and guide future work.

Core Features & Use Cases

  • Automatic extraction of impediments and root causes from completed work.
  • Level 1–3 classification and backlog filing to drive follow-up initiatives.
  • Meta-reflection and system-wide learning to improve the Kaizen process over time.

Quick Start

Run kaizen-reflect on a finished PR to generate a reflection summary.

Frequently Asked Questions about kaizen-reflect

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

FAQPage Schema
How do I automate post-project reflection to extract root causes and impediments?

Automating post-project reflection involves analyzing completed work to identify impediments, root causes, and actionable improvements. This Skill processes finished projects and files extracted follow-ups into a structured backlog for consistent process improvement.

What is the best way to classify process improvement actions from completed work?

Classifying process improvement actions uses a Level 1–3 tier system to categorize extracted outcomes. This structured approach files actionable follow-ups into the backlog, ensuring systematic tracking and driving future Kaizen initiatives.

How does meta-reflection improve Kaizen workflows over time?

Meta-reflection improves Kaizen workflows by surfacing system-wide learning data from completed projects. This mechanism updates the backlog with actionable insights, enabling continuous process refinement for future development cycles.

Can I generate a reflection summary directly from a completed pull request?

Generating a reflection summary from a completed pull request is fully supported. Running the automation on a finished PR extracts impediments and root causes, producing a structured summary for backlog filing.

When should I not use automated reflection for process improvement?

Automated reflection should not be used when a project is incomplete or lacks sufficient operational data. The mechanism requires finished work to accurately classify Level 1–3 outcomes and extract meaningful root causes for the backlog.