quality-nonconformance

Investigate non-conformances, perform root cause analysis, and manage CAPA workflows in regulated manufacturing.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill quality-nonconformance-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-nonconformance
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/quality-nonconformance
Command: npx skills add https://github.com/ibytechaos/claude --skill quality-nonconformance-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Quality engineers in regulated manufacturing (FDA, IATF 16949, AS9100) face complex non-conformance investigations, CAPA management, and SPC interpretation where mistakes create audit findings and regulatory risk. This Skill codifies 15+ years of senior quality engineering expertise into structured guidance for the full NCR lifecycle. ## Core Features & Use Cases - NCR Lifecycle Management: Guides identification, containment, documentation, MRB disposition (use-as-is, rework, repair, RTV, scrap), and closure per FDA 21 CFR 820.90 and IATF 16949 §8.7. - Root Cause Analysis & CAPA: Applies 5 Whys, Ishikawa, Fault Tree Analysis, and 8D methodology with red-flag detection for superficial investigations, plus CAPA effectiveness verification criteria. - SPC & Supplier Quality: Interprets control charts, Western Electric rules, capability indices (Cp/Cpk/Ppk), AQL sampling plans, and manages supplier escalation from SCAR through ASL removal. - Use Case: A lot of 10,000 molded components fails AQL sampling on a critical dimension. The Skill walks you through containment, supplier notification, tooling-wear root cause investigation, skip-lot suspension, and SCAR issuance. ## Quick Start Ask the assistant to investigate a non-conformance, for example by describing a failed incoming inspection lot and requesting a full NCR disposition and root cause analysis plan.

Frequently Asked Questions about quality-nonconformance

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

FAQPage Schema
How do I perform root cause analysis for a manufacturing non-conformance?

Select the method based on complexity: 5 Whys for simple single-cause failures, Ishikawa plus 5 Whys for multi-factor issues, 8D for recurring process problems, and Fault Tree Analysis for safety-critical events. Verify each cause with data rather than opinion, and never accept human error as a root cause.

What is the difference between corrective action and preventive action in CAPA?

Corrective action addresses an existing non-conformance and prevents its recurrence, while preventive action addresses a potential non-conformance identified through trend analysis or risk assessment. FDA expects both under 21 CFR 820.100, and conflating them is a common audit finding.

How do I interpret SPC control chart signals like Western Electric rules?

Rule 1 (one point beyond 3 sigma) demands immediate action, while Rules 2-4 (runs, trends, alternating patterns) indicate systematic causes requiring investigation before the process goes out of spec. A process within specification limits can still be out of control, so do not adjust for common cause variation.

When should I use 8D versus 5 Whys for problem solving?

Use 5 Whys for single events with a simple linear causal chain, budgeting 1-2 hours. Use the full 8D team-based methodology for recurring process issues or when automotive customers mandate it, budgeting 20-40 hours across all eight disciplines.

What are the disposition options for non-conforming material in an MRB?

The Material Review Board can disposition material as use-as-is (with engineering justification), rework to full conformance, repair with permanent deviation, return to vendor with a SCAR, or scrap with documented approval. Safety-critical characteristics cannot be used as-is without formal risk assessment and regulatory notification.

Why do CAPAs fail effectiveness verification after closure?

CAPAs typically fail because the original root cause analysis stopped at symptoms, such as blaming operator error and retraining as the fix. Verification confirms the action was implemented, but validation requires monitoring data over at least 90 days or three production lots showing zero recurrence.