kaizen-gaps

Identify and summarize systemic gaps across Kaizen issues, incidents, and horizons.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic analysis of kaizen issues and incidents to identify tooling gaps, testing gaps, horizon concentration, and unnamed dimensions. Produces prioritized lists for filing kaizens, writing feature PRDs, and writing meta/horizon PRDs. Triggers on "gap analysis", "analyze gaps", "what gaps do we have", "tooling gaps", "testing gaps", "horizon analysis", "where are problems concentrated".

Core Features & Use Cases

  • Surface root-cause clusters across the kaizen backlog to reveal high-value gaps for strategic planning.
  • Prioritize gaps for knowledge work like feature PRDs and horizon taxonomy updates.
  • Generate actionable outputs for filing kaizens, writing PRDs, and aligning horizons.

Quick Start

Run the kaizen-gaps skill against your project to produce prioritized lists for low-hanging gaps, PRD candidates, and horizon updates.

Frequently Asked Questions about kaizen-gaps

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

FAQPage Schema
How do I identify and prioritize systemic gaps from kaizen issues and incidents?

To identify and prioritize kaizen gaps, analyze systemic issues across incidents and horizons to reveal root-cause clusters, tooling gaps, and testing gaps. This process surfaces high-value opportunities for strategic planning and generates prioritized lists for filing kaizens and writing feature PRDs.

What is the best way to analyze backlog horizons and unnamed dimensions during sprint planning?

Analyzing backlog horizons involves applying gap-analysis techniques during sprint planning to reveal horizon concentrations and unnamed dimensions. This systematic review produces verified low-hanging kaizen gaps, concrete feature PRD candidates, and meta/horizon PRD candidates for prioritized improvement.

Can I generate feature PRD candidates from post-incident analysis?

Yes, you can generate concrete feature PRD candidates from post-incident analysis. By surfacing root-cause clusters across the kaizen backlog, the analysis translates systemic incidents and tooling gaps into actionable PRD candidates and meta/horizon taxonomy updates.

Does kaizen gap analysis work for periodic strategy reviews to find tooling and testing gaps?

Kaizen gap analysis works effectively for periodic strategy reviews by systematically examining kaizen issues to identify tooling gaps, testing gaps, and horizon concentration. It outputs prioritized lists for filing kaizens, writing feature PRDs, and aligning horizons for strategic planning.

When should I perform a gap analysis on my kaizen backlog?

Perform a kaizen backlog gap analysis during periodic strategy reviews, sprint planning, or post-incident analysis. Trigger the process when seeking to understand tooling gaps, testing gaps, horizon concentration, or where problems are concentrated to reveal high-value improvement opportunities.

What outputs should I expect from a kaizen gap analysis?

A kaizen gap analysis produces three outputs: verified low-hanging kaizen gaps for immediate filing, concrete feature PRD candidates for development, and meta/horizon PRD candidates for taxonomy updates. These prioritized lists align strategic improvement opportunities.