A SCAR works when the supplier receives facts it can investigate and deadlines it must meet, and when the
response is judged against clear criteria rather than accepted because it arrived. scripts/scar_check.py checks
both sides: the request before it is sent, and the supplier's response before it is accepted.
Trigger Conditions
Activate this skill when the user:
- Needs to issue a SCAR for a supplier nonconformity, repeat defect or audit finding
- Received a supplier's SCAR or 8D response and must accept or reject it
- Asks what to require from a supplier and by when
- Wants to know whether a supplier corrective action can be closed
The 8D format the supplier may use: 8d-problem-solving-report-writer; long-term improvement: supplier-development-plan-writer.
Workflow
1. DECIDE -> SCAR needed? (production or customer impact, repeat, safety, scorecard trigger)
2. WRITE -> requirement vs actual, quantity, evidence, impact, deadlines (writing-the-scar.md)
3. CHECK -> python scripts/scar_check.py scar.json (request only: "ready to send")
4. RESPONSE -> add the supplier's response to the JSON
5. EVALUATE -> python scripts/scar_check.py scar.json (ACCEPT / ACCEPT WITH COMMENTS / REJECT)
6. CLOSE -> only after effectiveness evidence; record on the scorecardChecks (scar_check.py)
| Code | Severity | Problem |
|---|---|---|
| SR001 | high | Problem lacks requirement, actual, quantity or evidence |
| SR002 | medium | Due dates missing or loose |
| SR101 | high | Containment incomplete or no clean point |
| SR102 | high | Occurrence or escape cause missing or human error |
| SR103 | high | Corrections or training only; a cause without action |
| SR104 | medium | No verification or effectiveness plan |
| SR105 | medium | No PFMEA / control plan update or read-across |
| SR106 | medium | Late response steps |
SR102 [high] occurrence cause 'Operator error during pouring' blames a person: why did the process allow it?
SR102 [high] no escape root cause (why was it not detected before shipping?)
Supplier response: REJECTWhen to issue, request content, an example problem statement and cost recovery: writing-the-scar.md. Accept / reject criteria per element, responding and escalation: evaluating-responses.md.
Output Format
For a request: the SCAR text (identification, problem, impact, required response and dates) and the check result. For a response: the verdict, the reasons per element, the new due dates for rejected items, and the closure criteria.
Scripts
python scripts/scar_check.py scar.jsonKeys: scar_id, supplier, part, issued, ncr_ref, problem (requirement, actual, quantity, evidence), due (containment, root_cause, closure), response (containment, containment_date, clean_point, occurrence_cause, escape_cause, cause_verification, actions with addresses occurrence/escape, effectiveness, fmea_control_plan, read_across, root_cause_date, closure_date). Exit codes: 0 request ready / response accepted, 1 incomplete request or rejected response, 2 read or JSON error.
Additional Resources
| File | Content |
|---|---|
| writing-the-scar.md | When to issue, request content, example, cost recovery |
| evaluating-responses.md | Accept / reject criteria, responding to the supplier, escalation |
8d-problem-solving-report-writer
Write and review 8D problem-solving reports for customer complaints and serious nonconformities (automotive and aerospace practice: Ford Global 8D, VDA, GM, Stellantis formats): D0 emergency response, D1 cross-functional team and champion, D2 problem description with 5W2H and is / is-not and no cause in the statement, D3 interim containment within 24 hours with verification and clean point, D4 verified occurrence and escape (non-detection) root causes plus systemic cause, D5 permanent corrective actions for each cause verified before implementation, D6 implementation, validation with production data and removal of containment, D7 PFMEA, control plan and read-across to similar products, D8 closure and recognition. Checks an 8D discipline by discipline for missing content, human-error root causes, missing escape cause or action, late containment and dates out of order.
acceptance-sampling-plan-selector
Select and evaluate acceptance sampling plans for incoming, in-process and final inspection: ANSI/ASQ Z1.4 / ISO 2859-1 single sampling under normal inspection (code letter from lot size and inspection level I, II, III, S-1 to S-4; sample size, Ac and Re from AQL, following the table's arrows to the correct plan; 100% when n reaches the lot size; AQLs above 10 per 100 units), operating characteristic curves (Pa at any quality, producer's quality level, indifference point, LTPD, AOQ and AOQL, binomial or hypergeometric), plans designed from producer and consumer risk, and c = 0 zero-acceptance plans. Covers AQL choice by defect class, switching rules between normal, tightened and reduced inspection, when sampling is not appropriate, and random sampling.
approved-supplier-list-manager
Manage and audit an approved supplier list (ASL) / external provider register for ISO 9001 8.4.1, IATF 16949 8.4 and AS9100 8.4.1: supplier status (approved, conditional, probation, pending, disqualified), scope of approval by commodity and process, risk class, certification and expiry, re-evaluation intervals by risk, conditions with end dates, single-source contingency, approver and customer-directed sources. Audits the list for expired or expiring certificates, overdue re-evaluations, conditional or probation status past its decision date, high-risk suppliers without the required certification, single-source suppliers without backup and missing approvers, and checks purchase orders for suppliers that are off-list, disqualified or pending, or buying outside the approved scope. Covers ERP blocks, PO requirements, off-list and emergency purchases.
apqp-phase-planner
Plan and track Advanced Product Quality Planning (AIAG APQP 3rd edition, IATF 16949) for a new or changed automotive part: back-schedule the five phases (plan and define, product design, process design, product and process validation, launch and feedback) from the start-of-production date by program complexity, with overlap, PPAP lead and safe-launch period; list the deliverables and gate for each phase (DFMEA, DVP&R, feasibility, process flow, PFMEA, control plans, MSA, Ppk, run at rate, PPAP, safe launch, lessons learned); adjust for build-to-print suppliers; flag compressed timelines and late or untracked deliverables against a status list. Covers gate reviews, red/yellow/green status reporting, run at rate and safe-launch exit criteria.
as9100-gap-analyzer
Run an AS9100D / EN 9100:2018 gap analysis for aviation, space and defence suppliers on the requirements added to ISO 9001: on-time delivery and conformity focus, management representative, ethics and human-factors awareness, operational planning and operational risk management, configuration management, product safety, counterfeit-part prevention, special requirements, critical items and key characteristics, external provider register and flow-down, FOD prevention, tooling and NC program control, special process validation, first article inspection (AS9102), traceability, in-service data and nonconforming product control. Generates and scores a worksheet, grades missing core controls as major, and checks invalid n/a claims. Covers AS9101/AS9104, OASIS, AS9102 FAI forms, counterfeit standards (AS5553, AS6174, AS6081), NADCAP and the planned IA9100 transition.
audit-report-writer
Write internal, supplier and pre-certification audit reports with the content ISO 19011:2018 6.5 expects: audit objectives, scope, criteria with revisions, dates, team and auditees, method and sampling statement, specific strengths, findings table and three-part finding details (requirement, evidence, statement), conclusion on the degree of fulfilment of criteria, diverging opinions, follow-up deadlines and distribution. Builds a Markdown report from a JSON audit record, generates the conclusion from the findings (major / minor / none) and flags reports missing required content or findings without clause or evidence. Covers conclusion wording, closing meetings, response expectations and verifying corrective actions.