problem-definition

Guide 5W2H and IS/IS NOT data capture for RCCA problem definitions.

10|5|Updated Jan 2, 2026

Search Tags:#workflow #root-cause #8d #rcca #problem-definition #is-is-not #5w2h

Ready to run

npx skills add https://github.com/ddunnock/claude-plugins --skill problem-definition

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: problem-definition
Source: https://github.com/ddunnock/claude-plugins/tree/main/skills/problem-definition
Command: npx skills add https://github.com/ddunnock/claude-plugins --skill problem-definition

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Problem Definition skill enables teams to convert scattered failure observations into precise, bounded RCCA problem statements using 5W2H and IS/IS NOT analysis, avoiding premature conclusions.

Core Features & Use Cases

Structured 5W2H capture: Collect What, Where, When, Who, How, and How Much, plus explicit IS/IS NOT boundaries.
RCCA workflow integration: Supports RCCA/8D framing, 5 Whys, and FMEA-informed context for root-cause investigations.
Use Case: When a nonconformance is observed, run an elicitation session that yields a complete, testable problem statement ready for investigation.

Quick Start

Launch the skill and provide initial information; the system will prompt with focused 5W2H questions and generate a complete problem definition.

Frequently Asked Questions about problem-definition

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

FAQPage Schema

How do I define a problem statement for root-cause analysis using 5W2H?▼

To define a problem statement for root-cause analysis using 5W2H, this skill guides you through structured data capture for What, Where, When, Who, How, and How Much, converting scattered observations into a precise, testable statement ready for investigation.

What is the IS/IS NOT method for 8D problem solving?▼

The IS/IS NOT method for 8D problem solving establishes clear boundaries around a nonconformance by defining what the issue is and what it is not, preventing premature conclusions and ensuring your RCCA investigation targets the correct failure.

How do I start a 5W2H elicitation session for manufacturing quality investigations?▼

To start a 5W2H elicitation session for manufacturing quality investigations, launch the skill and provide initial failure observations; the system will then prompt you with focused questions and generate a complete problem definition.

Can I use this RCCA workflow for supplier issues and machining nonconformances?▼

Yes, you can use this RCCA workflow for supplier issues, machining, and assembly nonconformances, as the problem definition framework applies structured 5W2H and IS/IS NOT boundary checks across diverse manufacturing quality investigations.

Does the problem definition skill integrate with FMEA and 5 Whys analysis?▼

Yes, the problem definition skill integrates with FMEA-informed context and supports RCCA framing to provide baseline data for 5 Whys analysis, ensuring your root-cause investigations have a bounded problem statement.

What is the best way to avoid premature conclusions during root-cause analysis?▼

The best way to avoid premature conclusions during root-cause analysis is applying IS/IS NOT boundary checks alongside structured 5W2H data capture, forcing teams to explicitly identify what falls outside the problem scope before investigating.