Write a nonconformance report that contains the fact, the containment, and the owner. Use when the user mentions NCR, nonconformance, quality escape, defect report, or asks for a NCR. Manufacturing and quality skill by Yasir Jilani.
Installs into .claude/skills of the current project.
Are you the author of Nonconformance Report?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/syasj-nonconformance-report)
---
name: nonconformance-report
description: "Write a nonconformance report that contains the fact, the containment, and the owner. Use when the user mentions NCR, nonconformance, quality escape, defect report, or asks for a NCR. Manufacturing and quality skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
author: Yasir Jilani
version: "1.0.0"
domain: manufacturing
---
<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
Edit the 'nonconformance-report' entry in source/, then run:
python3 scripts/generate.py && python3 scripts/validate.py
See CONTRIBUTING.md. -->
# Nonconformance Report
Write a nonconformance report that contains the fact, the containment, and the owner.
## When to use this skill
Use this skill when the user:
- NCR
- nonconformance
- quality escape
- defect report
## When not to use this skill
- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.
## Professional boundary
Quality and safety procedures are drafts for the site's quality system. Do not bypass a hold, calibration, or safety step.
## Operating boundaries
- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.
## Inputs to collect
- What failed
- Where it was found
- Quantity if known
- Immediate containment
## Workflow
### 1. Step 1
Describe the defect in observable terms.
### 2. Step 2
Record quantity and location only from their count.
### 3. Containment first
stop the escape path they named.
### 4. Step 4
Do not dispose of evidence they said must be kept.
### 5. Step 5
Separate containment from root-cause work.
### 6. Step 6
Assign an owner and a date. A report with no owner will age in a drawer.
## Output
Deliver a **NCR**.
- Purpose of this NCR, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.
## Quality bar
- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.
## Example
### Scenario
Gus Moretti, plant manager at Redline Parts in Nisku, needs a NCR by 30 September 2026. A report says 'bad parts' and the suspect lot is still being shipped.
### Example data
```text
From: Gus Moretti, plant manager
Organization: Redline Parts, Nisku
Date: 14 September 2026
Needed by: 30 September 2026
A report says 'bad parts' and the suspect lot is still being shipped.
What failed: Line 2, first seen 14 September 2026. No root cause recorded yet
Where it was found: Lot 26-0914, recorded 14 September 2026. No supporting file attached
Quantity if known: 40 in the last period. No prior period attached, so no trend
Immediate containment: Gauge 7 and one other, both unconfirmed as of 14 September 2026
```
### Example outcome
**Ncr**
To: Gus Moretti, plant manager, Redline Parts
Date: 14 September 2026 · Needed by: 30 September 2026
**Decision**
Stops the lot, describes the defect, and names the owner.
**What the file supports**
| Input | Value | Status |
| --- | --- | --- |
| What failed | Line 2, first seen 14 September 2026. No root cause recorded yet | Needs confirmation |
| Where it was found | Lot 26-0914, recorded 14 September 2026. No supporting file attached | Carried into the draft |
| Quantity if known | 40 in the last period. No prior period attached, so no trend | Carried into the draft |
| Immediate containment | Gauge 7 and one other, both unconfirmed as of 14 September 2026 | Needs confirmation |
**How this draft was built**
**1. Describe the defect in observable terms**
**2. Record quantity and location only from their count**
**3. Containment first**
stop the escape path they named.
**4. Do not dispose of evidence they said must be kept**
**5. Separate containment from root-cause work**
**Deliberately not done**
- A vague defect description.
- Disposing of required evidence.
- No containment.
**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.
Next: Gus Moretti by 30 September 2026. This is a draft, not a sign-off.
## Anti-patterns
- A vague defect description
- Disposing of required evidence
- No containment
## Related skills
- `capa-plan`
- `traceability-lot`