skills.rest
NeoLabHQ
NeoLabHQOFFICIAL
Explore all skills by this author →
WebsiteGitHub

analyse-problem

Generates A3 one-page problem analyses with root cause analysis and action plans.

1.5k|154|Updated Nov 13, 2025
Search Tags:#continuous improvement#incident analysis#kaizen#Problem Solving#Root Cause Analysis#5 whys#A3
One-click install
npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill analyse-problem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyse-problem
Source: https://github.com/NeoLabHQ/context-engineering-kit/tree/main/plugins/kaizen/skills/analyse-problem
Command: npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill analyse-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often document problems inconsistently, jump to solutions without finding root causes, and lose track of follow-up actions. This Skill structures problem analysis into the proven A3 format so every issue gets a complete, single-page treatment covering background through verification.

Core Features & Use Cases

  • Structured A3 Template: Produces a seven-section analysis covering Background, Current Condition, Goal, Root Cause Analysis, Countermeasures, Implementation Plan, and Follow-up.
  • Root Cause Methods: Integrates 5 Whys and Fishbone analysis to ensure countermeasures address causes rather than symptoms.
  • Use Case: When a production incident like database connection pool exhaustion recurs, invoke the Skill to produce a complete A3 document with measurable goals, a phased implementation plan with owners and timelines, and follow-up metrics to verify the fix.

Quick Start

Ask the agent to run /analyse-problem with a description of your issue, for example to analyze recurring API downtime during peak traffic hours.

Frequently Asked Questions about analyse-problem

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

FAQPage Schema
How do I write an A3 problem analysis report?▼

Provide a problem description to the analyse-problem command and it generates the full seven-section A3 format: background, current condition, goal, root cause analysis, countermeasures, implementation plan, and follow-up. Each section prompts for facts, data, and measurable targets.

What root cause analysis methods does A3 problem solving use?▼

The A3 format uses 5 Whys to drill from symptoms to the underlying cause and Fishbone (cause-and-effect) diagrams to map contributing factors across process, technology, people, and methods. Countermeasures must address the identified root causes.

When should I use A3 analysis versus a quick fix?▼

Use A3 for incidents, recurring issues, and major improvements where understanding root causes matters. It is overkill for small bugs, one-line fixes, or trivial issues where the documentation effort exceeds the problem's impact.

Can A3 analysis be used for security incidents?▼

Yes, the Skill includes a worked example for a critical SQL injection vulnerability covering emergency response, phased remediation, log review for exploitation, and prevention measures like SAST tooling and security training.

What output formats does the problem analysis support?▼

The Skill supports markdown or text output, with markdown as the default. The result is a structured single-page document that serves as a living record updated until the issue is closed.

Related Skills

Explore More Product & Management Skills→
junchenghuojunchenghuo
3

ops-observability-slo

Define SLO metrics, alert thresholds, and incident review processes.

Community
Intermediate
DevelopersGlobalDevelopersGlobal
65

meeting-notes-to-tasks

Convert meeting notes into action items with owners and due dates.

Official
Intermediate
cursorcursor
6.6k

principle-fix-root-causes

Guides debugging by tracing symptoms to root causes and fixing them there.

Official
Basic
mmbianco78mmbianco78

kaizen

Automate post-incident retrospectives with 5 Whys and PDCA cycles.

Community
Basic