Skip to content
Testing
Skill

/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.

From plugin
completely
616 skills9 agents

Claude Code

$ npx -y skills add 23ag1/completely --skill quality-nonconformance --agent claude-code

SKILL.md

quality-nonconformance.SKILL.md
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/affaan-m/everything-claude-code
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 ma
Read more
@23ag1
Ships withcompletely

A quality-first harness for autonomous AI coding agents. It turns "the agent said it's done" into *"here's the proof — graded by an independent, default-FAIL checker."* Done is earned, not asserted.

616 skills9 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
6
Star history of 23ag1/completely on GitHub, a chart by star-history.com

Other skills on completely.

auto

auto

Run completely AUTONOMOUSLY — loop the FULL task engine over the Beads queue, a fresh `claude -p` per task, until the queue is…

@23ag1@23ag1Install Skill
check

check

Run all configured quality checks (lint, types, tests) in one pass with terse output — reports "clean" when green, and only the…

@23ag1@23ag1Install Skill
completely

completely

Overview and entry point for the completely harness — a quality-first agent workflow unifying GSD (planning depth), Ralph…

@23ag1@23ag1Install Skill
control

control

Run completely UNDER CONTROL — execute the SINGLE next Beads task through the FULL task engine (understand → map → plan-check →…

@23ag1@23ag1Install Skill
init

init

Scaffold the completely thin layer into the current repository — Definition of Done, the harness rules snippet in CLAUDE.md, and…

@23ag1@23ag1Install Skill
plan

plan

Plan a phase or feature DIRECTLY into Beads — no PLAN.md, no markdown bridge. Runs GSD-style socratic discovery + decomposition +…

@23ag1@23ag1Install Skill

More skills from other plugins.

api-review

api-review

Produce the "Playwright 1.xx API Review" artifact for a range of commits - the public API additions and the breaking or behavior…

@microsoft@microsoftInstall Skill
add-e2e-selectors

add-e2e-selectors

Add reliable @grafana/e2e-selectors to interactive elements and key containers in the Grafana frontend. Use when adding e2e…

grafana5d78k
@grafana@grafanaInstall Skill
promptfoo-evals

promptfoo-evals

Write, refine, run, and QA promptfoo evaluation suites: promptfooconfig.yaml, prompts, providers, vars, tests, assertions,…

promptfoo13d27k
@promptfoo@promptfooInstall Skill
deepeval

deepeval

DeepEval evaluation workflow for AI agents and LLM applications. TRIGGER when the user wants to evaluate or improve an AI agent,…

@confident-ai@confident-aiInstall Skill

Questions about quality-nonconformance.

Which coding agents can use quality-nonconformance?
quality-nonconformance installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.