kaizen-evaluate

Evaluate kaizen issues by validating problem framing, scope, and evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate kaizen issues before implementation to ensure the problem statement is accurate, gather supporting incidents, and define a concrete scope and plan for admin alignment.

Core Features & Use Cases

  • Phase 0 validation: confirm the claimed problem exists and is testable.
  • Incident gathering: accumulate evidence from commits, issues, and discussions to quantify impact.
  • Observability assessment: determine what data would prove or disprove the problem.
  • Plan formation: craft a plan with clear success criteria and a high-level implementation path.
  • Stakeholder alignment: prepare artifacts for admin review and decision-making.

Quick Start

Run kaizen-evaluate to generate a concrete evaluation plan and prepare it for admin approval.

Frequently Asked Questions about kaizen-evaluate

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

FAQPage Schema
How do I validate problem scope before committing to implementation?

Validating problem scope requires evaluating the claimed issue to confirm it exists, gathering supporting incidents, and defining concrete success criteria. This ensures the problem framing is accurate and testable before development begins.

What is the best way to gather incident evidence for scope management?

Gathering incident evidence involves accumulating data from commits, issues, and discussions to quantify impact. This process assesses observability to determine what data proves or disproves the problem, ensuring inputs remain auditable for future iterations.

How do I form an implementation plan with clear success criteria?

Forming an implementation plan involves crafting a high-level path with defined success criteria after validating the problem scope. This produces artifacts suitable for admin review and decision-making, preparing the plan for subsequent implementation.

When do I need kaizen evaluation during admin planning?

Kaizen evaluation is needed during admin planning when you must align stakeholders before work begins. It confirms the problem statement is accurate, gathers evidence, and defines a concrete scope to prepare artifacts for admin approval.

Does kaizen evaluation work without prior observability data?

Kaizen evaluation includes an observability assessment to determine what data would prove or disprove the problem. If prior data is lacking, the evaluation identifies the specific evidence needed to validate the claimed issue before proceeding.

Why should I evaluate kaizen issues before implementation?

Evaluating kaizen issues before implementation ensures the problem framing is accurate and evidence supports the recommended path. This prevents wasted effort on unvalidated scopes and keeps all inputs auditable for future iterations.