kaizen-deep-dive

Identify root-cause patterns across Kaizen issues and generate a structured meta-issue.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies recurring root causes across clusters of Kaizen issues and generates a structured meta-issue that ties symptoms together and hands off to /kaizen-implement.

Core Features & Use Cases

  • Identifies shared root-cause patterns across related issues to reveal systemic problems.
  • Creates a well-structured GitHub meta-issue with a defined problem section, root-cause analysis, and linked symptoms for downstream work.
  • Facilitates a seamless handoff to /kaizen-implement to execute the meta-issue plan and drive unified improvements.

Quick Start

Summarize related kaizen issues, identify the root cause category, and create a meta-issue linking symptoms for handoff to /kaizen-implement.

Frequently Asked Questions about kaizen-deep-dive

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

FAQPage Schema
How do I group related Kaizen issues to find shared root causes?

Root-cause analysis identifies shared systemic patterns across a cluster of open Kaizen issues. It reveals underlying problems by connecting related symptoms, enabling structured issue tracking and unified improvement planning.

How do I create a structured meta-issue for root-cause analysis?

You create a meta-issue by generating a structured template containing a defined problem section, root-cause analysis, linked symptoms, and prevention tests. This provides metadata storage requirements for tracking unified improvements.

Can I hand off a meta-issue plan to automated implementation tools?

Yes, autonomous handoff to /kaizen-implement is supported. The skill generates a structured meta-issue with a plan template and metadata storage requirements, enabling seamless automated execution of the unified improvement plan.

What is the best way to track recurring issue patterns for software engineering improvements?

The best way is creating a meta-issue that links related symptoms and plans improvements through root-cause analysis. This approach identifies systemic patterns across open issues and drives unified prevention tests.

Do I need open Kaizen issues to use root-cause deep-dive analysis?

Yes, this analysis applies when a cluster of open Kaizen issues share a root cause. You need existing related issues to identify patterns, generate a structured meta-issue, and enable autonomous handoff to /kaizen-implement.