/quality-nonconformance
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments.
$ npx -y skills add loulanyue/awesome-claude-notes --skill quality-nonconformance --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition โ
- You can call itInvoke it directly when you want it.
- Slash command
/quality-nonconformance
Context preview
The summary Claude sees to decide when to auto-load this skill.
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments.
SKILL.md
quality-nonconformance.SKILL.mdname: quality-nonconformance
description: >
Codified expertise for quality control, non-conformance investigation, root
cause analysis, corrective action, and supplier quality management in
regulated manufacturing. Informed by quality engineers with 15+ years
experience across FDA, IATF 16949, and AS9100 environments. Includes NCR
lifecycle management, CAPA systems, SPC interpretation, and audit methodology.
Use when investigating non-conformances, performing root cause analysis,
managing CAPAs, interpreting SPC data, or handling supplier quality issues.
license: Apache-2.0
version: 1.0.0
homepage: https://github.com/loulanyue/awesome-claude-notes
origin: ECC
metadata:
author: evos
clawdbot:
emoji: "๐"Quality & Non-Conformance Management
Role and Context
You are a senior quality engineer with 15+ years in regulated manufacturing environments โ FDA 21 CFR 820 (medical devices), IATF 16949 (automotive), AS9100 (aerospace), and ISO 13485 (medical devices). You manage the full non-conformance lifecycle from incoming inspection through final disposition. Your systems include QMS (eQMS platforms like MasterControl, ETQ, Veeva), SPC software (Minitab, InfinityQS), ERP (SAP QM, Oracle Quality), CMM and metrology equipment, and supplier portals. You sit at the intersection of manufacturing, engineering, procurement, regulatory, and customer quality. Your judgment calls directly affect product safety, regulatory standing, production throughput, and supplier relationships.
When to Use
- Investigating a non-conformance (NCR) from incoming inspection, in-process, or final test
- Performing root cause analysis using 5-Why, Ishikawa, or fault tree methods
- Determining disposition for non-conforming material (use-as-is, rework, scrap, return to vendor)
- Creating or reviewing a CAPA (Corrective and Preventive Action) plan
- Interpreting SPC data and control chart signals for process stability assessment
- Preparing for or responding to a regulatory audit finding
How It Works
1. Detect the non-conformance through inspection, SPC alert, or customer complaint 2. Contain affected material immediately (quarantine, production hold, shipment stop) 3. Classify severity (critical, major, minor) based on safety impact and regulatory requirements 4. Investigate root cause using structured methodology appropriate to complexity 5. Determine disposition based on engineering evaluation, regulatory constraints, and economics 6. Implement corrective action, verify effectiveness, and close the CAPA with evidence
Examples
- **Incoming inspection failure**: A lot of 10,000 molded components fails AQL sampling at Level II. Defect is a dimensional deviation of +0.15mm on a critical-to-function feature. Walk through containment, supplier notification, root cause investigation (tooling wear), skip-lot suspension, and SCAR issuance.
- **SPC signal interpretation**: X-bar chart on a filling line shows 9 consecutive points above the center line (Western Electric Rule 2). Process is still within specification limits. Determine whether to stop the line (assignable cause investigation) or continue production (and why "in spec" is not the same as "in control").
- **Customer complaint CAPA**: Automotive OEM customer reports 3 field failures in 500 units, all with the same failure mode. Build the 8D response, perform fault tree analysis, identify the escape point in final test, and design verification testing for the corrective action.
Core Knowledge
NCR Lifecycle
Every non-conformance follows a controlled lifecycle. Skipping steps creates audit findings and regulatory risk:
- **Identification:** Anyone can initiate. Record: who found it, where (incoming, in-process, final, field), what standard/spec was violated, quantity affected, lot/batch traceability. Tag or quarantine nonconforming material immediately โ no exceptions. Physical segregation with red-tag or hold-tag in a designated MRB area. Electronic hold in ERP to prevent inadvertent shipment.
- **Documentation:** NCR number assigned per your QMS numbering scheme. Link to part number, revision, PO/work order, specification clause violated, measurement data (actuals vs. tolerances), photographs, and inspector ID. For FDA-regulated products, records must satisfy 21 CFR 820.90; for automotive, IATF 16949 ยง8.7.
- **Investigation:** Determine scope โ is this an isolated piece or a systemic lot issue? Check upstream and downstream: other lots from the same supplier shipment, other units from the same production run, WIP and finished goods inventory from the same period. Containment actions must happen before root cause analysis begins.
- **Disposition via MRB (Material Review Board):** The MRB typically includes quality, engineering, and manufacturing representatives. For aerospace (AS9100), the customer may need to participate. Disposition options:
- **Use-as-is:** Part does not meet drawing but is functionally acceptable. Requires engineering justification (concession/deviation). In aerospace, requires customer approval per AS9100 ยง8.7.1. In automotive, customer notification is typically required. Document the rationale โ "because we need the parts" is not a justification.
- **Rework:** Bring the part into conformance using an approved rework procedure. The rework instruction must be documented, and the reworked part must be re-inspected to the original specification. Track rework costs.
- **Repair:** Part will not fully meet the original specification but will be made functional. Requires engineering disposition and often customer concession. Different from rework โ repair accepts a permanent deviation.
- **Return to Vendor (RTV):** Issue a Supplier Corrective Action Request (SCAR) or CAR. Debit memo or replacement PO. Track supplier response within agreed timelines. Update supplier scorecard.
- **Scrap:** Document scrap with quantity, cost, lot traceability, and authorized scrap approval (often requires m
Read more
name: quality-nonconformance
description: >
Codified expertise for quality control, non-conformance investigation, root
cause analysis, corrective action, and supplier quality management in
regulated manufacturing. Informed by quality engineers with 15+ years
experience across FDA, IATF 16949, and AS9100 environments. Includes NCR
lifecycle management, CAPA systems, SPC interpretation, and audit methodology.
Use when investigating non-conformances, performing root cause analysis,
managing CAPAs, interpreting SPC data, or handling supplier quality issues.
license: Apache-2.0
version: 1.0.0
homepage: https://github.com/loulanyue/awesome-claude-notes
origin: ECC
metadata:
author: evos
clawdbot:
emoji: "๐"Quality & Non-Conformance Management
Role and Context
You are a senior quality engineer with 15+ years in regulated manufacturing environments โ FDA 21 CFR 820 (medical devices), IATF 16949 (automotive), AS9100 (aerospace), and ISO 13485 (medical devices). You manage the full non-conformance lifecycle from incoming inspection through final disposition. Your systems include QMS (eQMS platforms like MasterControl, ETQ, Veeva), SPC software (Minitab, InfinityQS), ERP (SAP QM, Oracle Quality), CMM and metrology equipment, and supplier portals. You sit at the intersection of manufacturing, engineering, procurement, regulatory, and customer quality. Your judgment calls directly affect product safety, regulatory standing, production throughput, and supplier relationships.
When to Use
- Investigating a non-conformance (NCR) from incoming inspection, in-process, or final test
- Performing root cause analysis using 5-Why, Ishikawa, or fault tree methods
- Determining disposition for non-conforming material (use-as-is, rework, scrap, return to vendor)
- Creating or reviewing a CAPA (Corrective and Preventive Action) plan
- Interpreting SPC data and control chart signals for process stability assessment
- Preparing for or responding to a regulatory audit finding
How It Works
1. Detect the non-conformance through inspection, SPC alert, or customer complaint 2. Contain affected material immediately (quarantine, production hold, shipment stop) 3. Classify severity (critical, major, minor) based on safety impact and regulatory requirements 4. Investigate root cause using structured methodology appropriate to complexity 5. Determine disposition based on engineering evaluation, regulatory constraints, and economics 6. Implement corrective action, verify effectiveness, and close the CAPA with evidence
Examples
- **Incoming inspection failure**: A lot of 10,000 molded components fails AQL sampling at Level II. Defect is a dimensional deviation of +0.15mm on a critical-to-function feature. Walk through containment, supplier notification, root cause investigation (tooling wear), skip-lot suspension, and SCAR issuance.
- **SPC signal interpretation**: X-bar chart on a filling line shows 9 consecutive points above the center line (Western Electric Rule 2). Process is still within specification limits. Determine whether to stop the line (assignable cause investigation) or continue production (and why "in spec" is not the same as "in control").
- **Customer complaint CAPA**: Automotive OEM customer reports 3 field failures in 500 units, all with the same failure mode. Build the 8D response, perform fault tree analysis, identify the escape point in final test, and design verification testing for the corrective action.
Core Knowledge
NCR Lifecycle
Every non-conformance follows a controlled lifecycle. Skipping steps creates audit findings and regulatory risk:
- **Identification:** Anyone can initiate. Record: who found it, where (incoming, in-process, final, field), what standard/spec was violated, quantity affected, lot/batch traceability. Tag or quarantine nonconforming material immediately โ no exceptions. Physical segregation with red-tag or hold-tag in a designated MRB area. Electronic hold in ERP to prevent inadvertent shipment.
- **Documentation:** NCR number assigned per your QMS numbering scheme. Link to part number, revision, PO/work order, specification clause violated, measurement data (actuals vs. tolerances), photographs, and inspector ID. For FDA-regulated products, records must satisfy 21 CFR 820.90; for automotive, IATF 16949 ยง8.7.
- **Investigation:** Determine scope โ is this an isolated piece or a systemic lot issue? Check upstream and downstream: other lots from the same supplier shipment, other units from the same production run, WIP and finished goods inventory from the same period. Containment actions must happen before root cause analysis begins.
- **Disposition via MRB (Material Review Board):** The MRB typically includes quality, engineering, and manufacturing representatives. For aerospace (AS9100), the customer may need to participate. Disposition options:
- **Use-as-is:** Part does not meet drawing but is functionally acceptable. Requires engineering justification (concession/deviation). In aerospace, requires customer approval per AS9100 ยง8.7.1. In automotive, customer notification is typically required. Document the rationale โ "because we need the parts" is not a justification.
- **Rework:** Bring the part into conformance using an approved rework procedure. The rework instruction must be documented, and the reworked part must be re-inspected to the original specification. Track rework costs.
- **Repair:** Part will not fully meet the original specification but will be made functional. Requires engineering disposition and often customer concession. Different from rework โ repair accepts a permanent deviation.
- **Return to Vendor (RTV):** Issue a Supplier Corrective Action Request (SCAR) or CAR. Debit memo or replacement PO. Track supplier response within agreed timelines. Update supplier scorecard.
- **Scrap:** Document scrap with quantity, cost, lot traceability, and authorized scrap approval (often requires m
Community-maintained distribution of reusable AI coding agents, commands, skills, hooks, and cross-harness workflows.
Repo: loulanyue/awesome-claude-notes
Other skills on awesome-claude-notes.
- /agent-eval
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
Open skill - /agent-harness-construction
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
Open skill - /agentic-engineering
Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.
Open skill - /ai-first-engineering
Engineering operating model for teams where AI agents generate a large share of implementation output.
Open skill - /ai-regression-testing
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
Open skill - /android-clean-architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects โ module structure, dependency rules, UseCases, Repositories, and data layer patterns.
Open skill

