Quality deviation report

Record manufacturing quality deviations with containment actions and investigation-ready traceability details.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill quality-deviation-report-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Quality deviation report
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/manufacturing/quality-deviation-report
Command: npx skills add https://github.com/vstorm-co/agenticos --skill quality-deviation-report-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a quality deviation is found on the shop floor, teams often write incomplete reports that pre-judge the cause or skip containment, making root-cause investigation impossible and widening recall risk. This Skill structures the deviation record so the investigation can actually happen. ## Core Features & Use Cases - Containment-first capture: Records what is affected (batch, lot, or serial range), where the material is now, whether it is on hold, and whether the process is stopped. - Structured deviation record: Documents observed versus specified values with measurements and tolerances, detection time, detector role, detection method, and the traceability chain back to material and supplier. - Suspect window definition: Establishes the last known-good check to bound how far back the deviation goes, flagging wider recall scope when it cannot be determined. - Use Case: An inspector finds a dimension out of tolerance on a machined part. Use this Skill to produce a deviation report that contains the affected lot, traces it to the supplier material, and defines the suspect window without recording a premature cause like "operator error". ## Quick Start Write a quality deviation report for batch 4471 where the measured diameter exceeded the specified tolerance during in-process inspection.

Frequently Asked Questions about Quality deviation report

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

FAQPage Schema
How do I write a quality deviation report in manufacturing?▼

Start with containment: identify the affected batch, lot, or serial range, locate the material including shipped goods, and state hold and process-stop status. Then record observed versus specified values with measurements, tolerances, detection details, and traceability to material and supplier.

What should a deviation report include for root cause investigation?▼

Include the measurement against the tolerance, when and by whom it was detected by role, how it was detected (inspection, in-process, or customer), and the traceability chain. Never record a cause in the report, since entries like "operator error" end the investigation prematurely.

How do I determine the scope of a quality deviation?▼

Find the last known-good check, which defines the suspect window for affected material. If that boundary cannot be established, state it explicitly, because an unknown window means a wider recall and hiding that fact is worse.

Should containment happen before or after the deviation report?▼

Containment happens in parallel with the report, not afterwards. The report's single job is to make the investigation possible, while containment actions like holds and process stops proceed at the same time.

Why should a deviation report not record a suspected cause?▼

Recording a cause pre-judges the investigation and biases the team toward that conclusion. Causes like "operator error" are almost never accurate and close down analysis before the traceability and measurement evidence is reviewed.