kaizen:analyse-problem

Analyze problems and document them in the A3 format.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dalawwa/labor-methods --skill kaizen-analyse-problem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen:analyse-problem
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/kaizen/skills/analyse-problem
Command: npx skills add https://github.com/dalawwa/labor-methods --skill kaizen-analyse-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A3 problem analysis provides a concise, structured approach to documenting problems, identifying root causes, and planning actionable countermeasures on a single page, enabling faster alignment and learning.

Core Features & Use Cases

  • Structured one-page A3 template with sections for Background, Current Condition, Goal/Target, Root Cause Analysis, Countermeasures, Implementation Plan, and Follow-up.
  • Step-by-step guidance and examples for incidents, recurring issues, and major improvements to drive focused problem-solving and continuous improvement.
  • Reusable artifact for post-incident reviews, process optimization, and team onboarding to standardized problem-solving practices.

Quick Start

Generate a completed A3 problem analysis document using the provided incident data.

Frequently Asked Questions about kaizen:analyse-problem

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

FAQPage Schema
What is A3 problem-solving and when should I use it?

A3 problem-solving is a structured, one-page format for documenting problems, identifying root causes, and planning countermeasures. Use it for incident analysis, recurring issues, and major process improvements to drive continuous improvement and team alignment.

How do I create an A3 report for root-cause analysis?

To create an A3 report for root-cause analysis, provide organized incident data to generate a one-page document. The analysis guides you sequentially through Background, Current Condition, Goal-Target, Root Cause Analysis, Countermeasures, Implementation Plan, and Follow-up.

What is the best way to document an incident for continuous improvement?

The best way to document an incident for continuous improvement is using a structured A3 one-page document. This approach concisely maps the background, current condition, root causes, countermeasures, implementation plan, and follow-up for focused problem-solving.

What format does incident data need to be in for A3 analysis?

Incident data requires an organized input set to generate a complete A3 one-page plan. Providing structured incident details ensures the output includes a well-structured root-cause analysis and actionable implementation steps.

Can I use A3 analysis for process optimization and post-incident reviews?

Yes, you can use A3 analysis for process optimization and post-incident reviews. The generated one-page document serves as a reusable artifact for post-incident reviews, process improvement, and standardizing team problem-solving practices.