[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD69VN1FTX52KTJWP144QQ":3,"skill-same:01M6MD69VN1FTX52KTJWP144QQ":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6MD69VN1FTX52KTJWP144QQ","iatf-16949-audit",null,"Conduct an IATF audit, check supplemental requirements, or prepare for a manufacturing process audit or IATF 16949:2016 third-party assessment. Covers customer-specific requirements (CSR), all 16 automotive supplemental clauses, and the three required audit types: QMS audit, manufacturing process audit, and product audit. Use for internal IATF audits or supplier quality audits at automotive organisations.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Faudit\u002Fiatf-16949-audit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"audit","iatf 16949 audit","third-party","2026","automotive","conduct","party","for","at","types","electronics","manufacturing","customer","requirements","three","use","process","check","quality","engineering","product","assessment","2026-11-10 10:12:30",false,"---\nname: iatf-16949-audit\ndescription: >-\n  Conduct an IATF audit, check supplemental requirements, or prepare for a manufacturing\n  process audit or IATF 16949:2016 third-party assessment. Covers customer-specific\n  requirements (CSR), all 16 automotive supplemental clauses, and the three required audit\n  types: QMS audit, manufacturing process audit, and product audit. Use for internal IATF\n  audits or supplier quality audits at automotive organisations.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iatf-16949: \"9.2.2\"\n  domain: quality-engineering\n  subdomain: audit\n  industries: automotive,electronics\n  status: approved\n  created: \"2026-06-01\"\n  last_updated: \"2026-06-03\"\n  updated_by: migmcc\n  reviewed_by: RBraga01\n  standard_edition: \"IATF 16949:2016\"\n---\n\n# IATF 16949:2016 Internal Audit — Supplemental Requirements\n\n## Goal\n\nAudit the automotive-specific supplemental requirements of IATF 16949:2016, including CSR compliance and the three mandatory internal audit streams. Use in conjunction with [iso-9001-internal-audit](..\u002Fiso-9001-internal-audit\u002F) for a complete IATF audit.\n\n---\n\n## When to use\n\nThis skill covers the **IATF 16949 supplemental requirements** — the automotive additions to ISO 9001.\n\nIATF 16949 requires three types of internal audit (§9.2.2.1). All three must be planned, executed, and recorded within the audit programme cycle:\n\n1. **QMS audit** — covers the entire quality management system (ISO 9001 + IATF supplementals)\n2. **Manufacturing process audit** — process-based, covers all manufacturing processes at least annually\n3. **Product audit** — product-specific, verifies product conformance to specifications\n\nAll manufacturing processes must be audited at least annually, with increased frequency for high-risk or poor-performing areas.\n\n---\n\n## Required IATF Audit Checklist\n\n☐ Verify all three audit streams are planned and executed within the programme cycle\n☐ Confirm CSR register is current and that changes trigger QMS document updates\n☐ Check contingency plans are documented, reviewed, and tested (not just written)\n☐ Verify special characteristics are consistent across all documents (drawing, DFMEA, PFMEA, CP, WI)\n☐ Confirm supplier monitoring and escalation are active with defined thresholds\n☐ Check Control Plan ↔ PFMEA linkage is current\n☐ Verify traceability and suspect material isolation capability (24-hour test)\n☐ Review temporary deviations for approval, expiry, and active control\n☐ Verify problem-solving methodology is applied with objective evidence of effectiveness\n☐ Confirm management review includes all IATF supplemental inputs\n☐ Do not accept verbal confirmation — verify by observing the process, interviewing personnel, and reviewing records\n\n---\n\n## Key IATF 16949 supplemental requirements — audit questions\n\n### §4.3.2 — Customer-specific requirements (CSR)\n\nThis is the most commonly non-conforming IATF clause.\n\nQuestions:\n\n- Is there a register of all applicable customer-specific requirements (CSRs)?\n- For each OEM customer: have the latest CSRs been downloaded and reviewed?\n- Are CSR requirements addressed in the QMS (procedures, control plans, work instructions)?\n- Are personnel who deal with each customer aware of their specific requirements?\n- CSR review must be revision-controlled and linked to implementation evidence in affected documents — is this traceable?\n- *Evidence:* CSR register, evidence that each CSR has been reviewed and implemented, CSR revision dates vs. QMS document dates\n\n**High-risk CSR areas:** PPAP requirements, problem-solving format requirements, special characteristics symbols, labelling specifications, sub-supplier approval requirements.\n\n---\n\n### §5.1.1.1 — Corporate responsibility\n\n- Is there a documented corporate responsibility policy (ethics, anti-bribery)?\n- Is there an escalation process for reporting ethical concerns?\n- Are employees aware of how to report ethical concerns confidentially?\n- *Evidence:* code of conduct, ethics policy, reporting mechanism (hotline or similar)\n\n---\n\n### §5.3.1 — Organisational roles, responsibilities, and authorities — supplemental\n\n- Is there a person responsible for customer satisfaction?\n- Are responsibilities for special characteristics defined?\n- Is there a process for communicating customer requirements to all relevant functions?\n- *Evidence:* roles matrix with customer satisfaction ownership identified\n\n---\n\n### §6.1.2.1 — Risk analysis (supplemental)\n\n- Does the risk analysis consider lessons learned from similar products?\n- Is warranty data, field returns, and customer complaints included as inputs?\n- *Evidence:* risk analysis records with warranty\u002Ffield data inputs\n\n---\n\n### §6.1.2.3 — Contingency plans\n\nIATF requires documented contingency plans for:\n\n- Key equipment failure\n- Key supplier failure or disruption\n- Labour shortages\n- IT\u002Finfrastructure failure\n- Natural disasters or site incidents affecting delivery\n\nQuestions:\n\n- Are contingency plans documented for each of these scenarios?\n- Are plans reviewed periodically (at least annually)?\n- Are they tested or rehearsed?\n- Does top management know who activates contingency plans?\n- Do contingency plans include customer communication protocols and recovery priorities?\n- *Evidence:* contingency plan document, last review date, test\u002Fsimulation records\n\n---\n\n### §7.2.3 — Internal auditor competency\n\n- Are internal auditors formally qualified or trained?\n- Do auditors have process knowledge for the areas they audit?\n- Is there evidence of auditor training (certification, OJT, qualification test)?\n- Are auditors independent of the area they audit?\n- Is auditor effectiveness periodically reviewed based on audit quality and finding accuracy?\n- *Evidence:* auditor qualification records, audit schedule showing independence\n\n---\n\n### §7.2.4 — Second and third-party auditor competency\n\n- For supplier audits: are supplier auditors trained and qualified?\n- For customer audits: are there designated contacts?\n\n---\n\n### §8.3.2.1 — Design and development — supplemental\n\n- Are special characteristics (SC) identified and documented in DFMEA and drawings?\n- Are customer-specific SC symbols used correctly?\n- Are SC characteristics flowed down to PFMEA, Control Plan, and work instructions?\n- *Evidence:* drawing with SC marked, DFMEA with SC, PFMEA with SC, Control Plan with SC, WI with SC\n\n---\n\n### §8.3.3.3 — Special characteristics\n\n- Is there a process to identify, document, and control all special characteristics?\n- Do all documents (drawing, DFMEA, PFMEA, CP, WI) use consistent SC symbols?\n- Are operators aware of which characteristics are special?\n- Any inconsistency in SC identification across documents must be treated as a significant audit finding due to control failure — is SC consistency actively verified?\n- *Evidence:* SC registry or matrix cross-referencing all documents\n\n---\n\n### §8.4.1.2 — Customer-directed sources (directed buy)\n\n- When the customer directs a specific supplier (directed buy), is this documented?\n- Is the directed supplier included in the approved supplier list?\n- Is quality monitoring applied even if the customer selected the supplier?\n\n---\n\n### §8.4.2.3 — Supplier monitoring\n\nIATF requires active supplier monitoring with specific actions for non-performing suppliers.\n\nQuestions:\n\n- Is there a supplier performance monitoring system (PPM, on-time delivery, quality issues)?\n- Is supplier performance reviewed at a defined frequency (minimum quarterly)?\n- Are supplier development or escalation actions triggered based on defined performance thresholds?\n- For poor performers: is there a documented escalation and improvement process?\n- Are suppliers assessed for delivery of conforming product (not just quality level)?\n- *Evidence:* supplier scorecards, last 4 quarters of performance data, improvement plans for poor performers\n\n---\n\n### §8.5.1.1 — Control plan\n\nQuestions:\n\n- Is there a control plan for each production part?\n- Does it cover: pre-launch, production, and reaction plan?\n- Are all special characteristics in the control plan with specific control methods?\n- Is the control plan linked to the PFMEA (detection controls match)?\n- Are reaction plans in the Control Plan understood and applied at the point of use — not only documented?\n- Was it updated after the last process or product change?\n- *Evidence:* control plan, PFMEA (verify linkage), latest revision date vs. last process change date\n\n---\n\n### §8.5.2.1 — Identification and traceability — supplemental\n\n- Is full traceability from raw material to finished product maintained?\n- Can suspect material be isolated within 24 hours?\n- Is there a procedure for handling suspect material?\n- Are lot sizes defined to limit the scope of recalls?\n- *Evidence:* traceability records, suspect material handling procedure, sample traceability exercise (ask for a part and trace it backwards)\n\n---\n\n### §8.5.6.1.1 — Control of changes — supplemental (temporary change)\n\nIATF requires that temporary process changes (deviations) be strictly controlled.\n\nQuestions:\n\n- Is there a process for managing temporary deviations (substituting a process step or material)?\n- Are deviations approved in writing with defined expiry dates?\n- Is there a register of all open temporary deviations?\n- Are expired deviations actively closed or extended — not left open silently?\n- Is the customer notified when required by their CSR?\n- *Evidence:* deviation register, sample open deviation with expiry date and approval\n\n---\n\n### §8.7.1.1 — Customer notification\n\n- Is there a procedure for notifying the customer when suspect material may have been shipped?\n- Does it define when notification is required (not just when the customer asks)?\n- Does the procedure specify notification timelines (e.g., 24 hours for safety-related escapes per CSR)?\n- Has the procedure been triggered recently? Were notifications timely?\n- *Evidence:* notification procedure, last notification records (if any)\n\n---\n\n### §9.2.2.1 — Internal audit programme — supplemental\n\nIATF requires **three audit streams** — most organisations fail by only conducting clause-based audits:\n\n1. **QMS audit** — covers clauses; must cover entire QMS within the audit programme cycle\n2. **Manufacturing process audit** — process-based, all manufacturing processes annually minimum; uses VDA 6.3 or equivalent scoring\n3. **Product audit** — product\u002Fshipment audits at defined frequency\n\nQuestions:\n\n- Are all three audit types in the programme?\n- Is the manufacturing process audit process-based (turtle diagram approach)?\n- Are all processes and products covered within the audit cycle?\n- Is the audit programme risk-based (higher risk = higher audit frequency)?\n- Low process audit scores must trigger corrective action, management review, and re-audit planning — is this in place?\n- *Evidence:* annual audit programme, audit reports for all three types, process audit records (not just clause audits)\n\n---\n\n### §9.3.2.1 — Management review — supplemental inputs\n\nIATF management review must include (in addition to ISO 9001 §9.3.2):\n\n- Cost of poor quality (COPQ)\n- Warranty performance (if applicable)\n- Customer satisfaction and field performance review\n- Status of CSR compliance\n- Manufacturing feasibility assessments\n\nQuestions:\n\n- Are these topics covered in the management review agenda?\n- Is there data for each topic?\n- Are decisions from these IATF-specific inputs translated into actions with owners and due dates?\n- *Evidence:* management review minutes with IATF-required topics explicitly addressed\n\n---\n\n### §10.2.3 — Problem solving\n\n- Is there a documented problem-solving methodology (8D or equivalent)?\n- Is the methodology applied consistently across all quality escapes?\n- Does the 8D identify root cause of occurrence AND root cause of escape?\n- Is effectiveness verified before closure?\n- *Evidence:* problem-solving procedure, sample 8D reports, verification of effectiveness records\n\n---\n\n### §10.2.4 — Error proofing\n\n- Is there a documented approach to applying error-proofing (poka-yoke)?\n- Are poka-yoke devices tested at defined intervals (IATF requires: minimum at every start of production)?\n- Are test records maintained?\n- Are failed or bypassed error-proofing checks treated as production stop \u002F reaction plan triggers where applicable?\n- Are poka-yoke failures treated as non-conformances requiring CAPA?\n- *Evidence:* poka-yoke register, test frequency, test records, last test date vs. interval\n\n---\n\n### §10.3.1 — Continual improvement plan\n\n- Is there a formal, documented continual improvement plan?\n- Does it include manufacturing process effectiveness (not just quality KPIs)?\n- Is it reviewed at management review?\n- *Evidence:* CI plan document, last review, evidence of CI activities\n\n---\n\n## Product audit — §9.2.2.3\n\nA product audit verifies that finished products meet all requirements before shipment. It is one of the three mandatory IATF audit streams.\n\nFocus areas for product audit:\n\n- Product conformity to drawing and specification (dimensional, functional, visual)\n- Packaging and labelling compliance (OEM label format, part number, revision, quantity)\n- Traceability and release status (is the product formally released and traceable to its records?)\n- Audit frequency based on risk, customer issues, and product criticality\n\nEvidence required: product audit reports, measurement records, packaging inspection records, release documentation.\n\n---\n\n## Manufacturing process audit — turtle diagram approach\n\nA manufacturing process audit (required annually for each process) uses a turtle diagram to assess:\n\n| Input | Question |\n|-------|---------|\n| **Who** (Man) | Qualification requirements, training, availability |\n| **With what** (Machine) | Equipment capability, maintenance, calibration |\n| **Using what method** | Work instructions, current, at point of use |\n| **With what material** | Incoming material control, traceability |\n| **With what measurement** | Gauges, MSA, SPC |\n| **Environment** | Cleanroom, temperature, ESD, contamination |\n| **Process output** | First-pass yield, defect rate, scrap |\n| **Customer feedback** | PPM, complaints, warranty |\n\nFor each element: is it adequate? Is it controlled? Is there objective evidence?\n\nEach turtle element should be verified by direct observation, interview, and record review — not by document review alone.\n\nA process audit must result in a process audit score (VDA 6.3 uses a percentage score by process element P1-P7). Low scores must trigger corrective action, management review input, and re-audit planning.\n\n---\n\n## Common IATF audit failures\n\n1. **CSR register not updated** when customer publishes new CSR revision\n2. **No manufacturing process audits** — only clause-based audits in the programme\n3. **Contingency plans exist but were never tested**\n4. **Temporary deviations without expiry dates** or expired deviations not closed\n5. **SC not consistently marked** across drawing, PFMEA, control plan, and work instruction\n6. **Error-proofing not tested** at every start of production (frequency not defined or records not kept)\n7. **Problem-solving procedure exists** but CARs in practice skip root cause or VOE\n\n## Output Format\n\nAt the start of each use, ask the user:\n\n> \"How would you like to receive the output?\n> **A** — Structured Markdown (formatted tables and sections, ready to copy)\n> **B** — Plain tables (simplified structure for Excel or Word)\n> **C** — Narrative report (flowing text for a formal document or email)\n>\n> Default: A.\"\n\nAdapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.\n\n## Reference files\n\n- [IATF supplemental requirements checklist](references\u002Fsupplemental-requirements.md)\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-01 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-03 | @migmcc | Added supplemental requirements reference and CSR audit coverage |\n","# IATF 16949:2016 Internal Audit — Supplemental Requirements\n\n## Goal\n\nAudit the automotive-specific supplemental requirements of IATF 16949:2016, including CSR compliance and the three mandatory internal audit streams. Use in conjunction with [iso-9001-internal-audit](..\u002Fiso-9001-internal-audit\u002F) for a complete IATF audit.\n\n---\n\n## When to use\n\nThis skill covers the **IATF 16949 supplemental requirements** — the automotive additions to ISO 9001.\n\nIATF 16949 requires three types of internal audit (§9.2.2.1). All three must be planned, executed, and recorded within the audit programme cycle:\n\n1. **QMS audit** — covers the entire quality management system (ISO 9001 + IATF supplementals)\n2. **Manufacturing process audit** — process-based, covers all manufacturing processes at least annually\n3. **Product audit** — product-specific, verifies product conformance to specifications\n\nAll manufacturing processes must be audited at least annually, with increased frequency for high-risk or poor-performing areas.\n\n---\n\n## Required IATF Audit Checklist\n\n☐ Verify all three audit streams are planned and executed within the programme cycle\n☐ Confirm CSR register is current and that changes trigger QMS document updates\n☐ Check contingency plans are documented, reviewed, and tested (not just written)\n☐ Verify special characteristics are consistent across all documents (drawing, DFMEA, PFMEA, CP, WI)\n☐ Confirm supplier monitoring and escalation are active with defined thresholds\n☐ Check Control Plan ↔ PFMEA linkage is current\n☐ Verify traceability and suspect material isolation capability (24-hour test)\n☐ Review temporary deviations for approval, expiry, and active control\n☐ Verify problem-solving methodology is applied with objective evidence of effectiveness\n☐ Confirm management review includes all IATF supplemental inputs\n☐ Do not accept verbal confirmation — verify by observing the process, interviewing personnel, and reviewing records\n\n---\n\n## Key IATF 16949 supplemental requirements — audit questions\n\n### §4.3.2 — Customer-specific requirements (CSR)\n\nThis is the most commonly non-conforming IATF clause.\n\nQuestions:\n\n- Is there a register of all applicable customer-specific requirements (CSRs)?\n- For each OEM customer: have the latest CSRs been downloaded and reviewed?\n- Are CSR requirements addressed in the QMS (procedures, control plans, work instructions)?\n- Are personnel who deal with each customer aware of their specific requirements?\n- CSR review must be revision-controlled and linked to implementation evidence in affected documents — is this traceable?\n- *Evidence:* CSR register, evidence that each CSR has been reviewed and implemented, CSR revision dates vs. QMS document dates\n\n**High-risk CSR areas:** PPAP requirements, problem-solving format requirements, special characteristics symbols, labelling specifications, sub-supplier approval requirements.\n\n---\n\n### §5.1.1.1 — Corporate responsibility\n\n- Is there a documented corporate responsibility policy (ethics, anti-bribery)?\n- Is there an escalation process for reporting ethical concerns?\n- Are employees aware of how to report ethical concerns confidentially?\n- *Evidence:* code of conduct, ethics policy, reporting mechanism (hotline or similar)\n\n---\n\n### §5.3.1 — Organisational roles, responsibilities, and authorities — supplemental\n\n- Is there a person responsible for customer satisfaction?\n- Are responsibilities for special characteristics defined?\n- Is there a process for communicating customer requirements to all relevant functions?\n- *Evidence:* roles matrix with customer satisfaction ownership identified\n\n---\n\n### §6.1.2.1 — Risk analysis (supplemental)\n\n- Does the risk analysis consider lessons learned from similar products?\n- Is warranty data, field returns, and customer complaints included as inputs?\n- *Evidence:* risk analysis records with warranty\u002Ffield data inputs\n\n---\n\n### §6.1.2.3 — Contingency plans\n\nIATF requires documented contingency plans for:\n\n- Key equipment failure\n- Key supplier failure or disruption\n- Labour shortages\n- IT\u002Finfrastructure failure\n- Natural disasters or site incidents affecting delivery\n\nQuestions:\n\n- Are contingency plans documented for each of these scenarios?\n- Are plans reviewed periodically (at least annually)?\n- Are they tested or rehearsed?\n- Does top management know who activates contingency plans?\n- Do contingency plans include customer communication protocols and recovery priorities?\n- *Evidence:* contingency plan document, last review date, test\u002Fsimulation records\n\n---\n\n### §7.2.3 — Internal auditor competency\n\n- Are internal auditors formally qualified or trained?\n- Do auditors have process knowledge for the areas they audit?\n- Is there evidence of auditor training (certification, OJT, qualification test)?\n- Are auditors independent of the area they audit?\n- Is auditor effectiveness periodically reviewed based on audit quality and finding accuracy?\n- *Evidence:* auditor qualification records, audit schedule showing independence\n\n---\n\n### §7.2.4 — Second and third-party auditor competency\n\n- For supplier audits: are supplier auditors trained and qualified?\n- For customer audits: are there designated contacts?\n\n---\n\n### §8.3.2.1 — Design and development — supplemental\n\n- Are special characteristics (SC) identified and documented in DFMEA and drawings?\n- Are customer-specific SC symbols used correctly?\n- Are SC characteristics flowed down to PFMEA, Control Plan, and work instructions?\n- *Evidence:* drawing with SC marked, DFMEA with SC, PFMEA with SC, Control Plan with SC, WI with SC\n\n---\n\n### §8.3.3.3 — Special characteristics\n\n- Is there a process to identify, document, and control all special characteristics?\n- Do all documents (drawing, DFMEA, PFMEA, CP, WI) use consistent SC symbols?\n- Are operators aware of which characteristics are special?\n- Any inconsistency in SC identification across documents must be treated as a significant audit finding due to control failure — is SC consistency actively verified?\n- *Evidence:* SC registry or matrix cross-referencing all documents\n\n---\n\n### §8.4.1.2 — Customer-directed sources (directed buy)\n\n- When the customer directs a specific supplier (directed buy), is this documented?\n- Is the directed supplier included in the approved supplier list?\n- Is quality monitoring applied even if the customer selected the supplier?\n\n---\n\n### §8.4.2.3 — Supplier monitoring\n\nIATF requires active supplier monitoring with specific actions for non-performing suppliers.\n\nQuestions:\n\n- Is there a supplier performance monitoring system (PPM, on-time delivery, quality issues)?\n- Is supplier performance reviewed at a defined frequency (minimum quarterly)?\n- Are supplier development or escalation actions triggered based on defined performance thresholds?\n- For poor performers: is there a documented escalation and improvement process?\n- Are suppliers assessed for delivery of conforming product (not just quality level)?\n- *Evidence:* supplier scorecards, last 4 quarters of performance data, improvement plans for poor performers\n\n---\n\n### §8.5.1.1 — Control plan\n\nQuestions:\n\n- Is there a control plan for each production part?\n- Does it cover: pre-launch, production, and reaction plan?\n- Are all special characteristics in the control plan with specific control methods?\n- Is the control plan linked to the PFMEA (detection controls match)?\n- Are reaction plans in the Control Plan understood and applied at the point of use — not only documented?\n- Was it updated after the last process or product change?\n- *Evidence:* control plan, PFMEA (verify linkage), latest revision date vs. last process change date\n\n---\n\n### §8.5.2.1 — Identification and traceability — supplemental\n\n- Is full traceability from raw material to finished product maintained?\n- Can suspect material be isolated within 24 hours?\n- Is there a procedure for handling suspect material?\n- Are lot sizes defined to limit the scope of recalls?\n- *Evidence:* traceability records, suspect material handling procedure, sample traceability exercise (ask for a part and trace it backwards)\n\n---\n\n### §8.5.6.1.1 — Control of changes — supplemental (temporary change)\n\nIATF requires that temporary process changes (deviations) be strictly controlled.\n\nQuestions:\n\n- Is there a process for managing temporary deviations (substituting a process step or material)?\n- Are deviations approved in writing with defined expiry dates?\n- Is there a register of all open temporary deviations?\n- Are expired deviations actively closed or extended — not left open silently?\n- Is the customer notified when required by their CSR?\n- *Evidence:* deviation register, sample open deviation with expiry date and approval\n\n---\n\n### §8.7.1.1 — Customer notification\n\n- Is there a procedure for notifying the customer when suspect material may have been shipped?\n- Does it define when notification is required (not just when the customer asks)?\n- Does the procedure specify notification timelines (e.g., 24 hours for safety-related escapes per CSR)?\n- Has the procedure been triggered recently? Were notifications timely?\n- *Evidence:* notification procedure, last notification records (if any)\n\n---\n\n### §9.2.2.1 — Internal audit programme — supplemental\n\nIATF requires **three audit streams** — most organisations fail by only conducting clause-based audits:\n\n1. **QMS audit** — covers clauses; must cover entire QMS within the audit programme cycle\n2. **Manufacturing process audit** — process-based, all manufacturing processes annually minimum; uses VDA 6.3 or equivalent scoring\n3. **Product audit** — product\u002Fshipment audits at defined frequency\n\nQuestions:\n\n- Are all three audit types in the programme?\n- Is the manufacturing process audit process-based (turtle diagram approach)?\n- Are all processes and products covered within the audit cycle?\n- Is the audit programme risk-based (higher risk = higher audit frequency)?\n- Low process audit scores must trigger corrective action, management review, and re-audit planning — is this in place?\n- *Evidence:* annual audit programme, audit reports for all three types, process audit records (not just clause audits)\n\n---\n\n### §9.3.2.1 — Management review — supplemental inputs\n\nIATF management review must include (in addition to ISO 9001 §9.3.2):\n\n- Cost of poor quality (COPQ)\n- Warranty performance (if applicable)\n- Customer satisfaction and field performance review\n- Status of CSR compliance\n- Manufacturing feasibility assessments\n\nQuestions:\n\n- Are these topics covered in the management review agenda?\n- Is there data for each topic?\n- Are decisions from these IATF-specific inputs translated into actions with owners and due dates?\n- *Evidence:* management review minutes with IATF-required topics explicitly addressed\n\n---\n\n### §10.2.3 — Problem solving\n\n- Is there a documented problem-solving methodology (8D or equivalent)?\n- Is the methodology applied consistently across all quality escapes?\n- Does the 8D identify root cause of occurrence AND root cause of escape?\n- Is effectiveness verified before closure?\n- *Evidence:* problem-solving procedure, sample 8D reports, verification of effectiveness records\n\n---\n\n### §10.2.4 — Error proofing\n\n- Is there a documented approach to applying error-proofing (poka-yoke)?\n- Are poka-yoke devices tested at defined intervals (IATF requires: minimum at every start of production)?\n- Are test records maintained?\n- Are failed or bypassed error-proofing checks treated as production stop \u002F reaction plan triggers where applicable?\n- Are poka-yoke failures treated as non-conformances requiring CAPA?\n- *Evidence:* poka-yoke register, test frequency, test records, last test date vs. interval\n\n---\n\n### §10.3.1 — Continual improvement plan\n\n- Is there a formal, documented continual improvement plan?\n- Does it include manufacturing process effectiveness (not just quality KPIs)?\n- Is it reviewed at management review?\n- *Evidence:* CI plan document, last review, evidence of CI activities\n\n---\n\n## Product audit — §9.2.2.3\n\nA product audit verifies that finished products meet all requirements before shipment. It is one of the three mandatory IATF audit streams.\n\nFocus areas for product audit:\n\n- Product conformity to drawing and specification (dimensional, functional, visual)\n- Packaging and labelling compliance (OEM label format, part number, revision, quantity)\n- Traceability and release status (is the product formally released and traceable to its records?)\n- Audit frequency based on risk, customer issues, and product criticality\n\nEvidence required: product audit reports, measurement records, packaging inspection records, release documentation.\n\n---\n\n## Manufacturing process audit — turtle diagram approach\n\nA manufacturing process audit (required annually for each process) uses a turtle diagram to assess:\n\n| Input | Question |\n|-------|---------|\n| **Who** (Man) | Qualification requirements, training, availability |\n| **With what** (Machine) | Equipment capability, maintenance, calibration |\n| **Using what method** | Work instructions, current, at point of use |\n| **With what material** | Incoming material control, traceability |\n| **With what measurement** | Gauges, MSA, SPC |\n| **Environment** | Cleanroom, temperature, ESD, contamination |\n| **Process output** | First-pass yield, defect rate, scrap |\n| **Customer feedback** | PPM, complaints, warranty |\n\nFor each element: is it adequate? Is it controlled? Is there objective evidence?\n\nEach turtle element should be verified by direct observation, interview, and record review — not by document review alone.\n\nA process audit must result in a process audit score (VDA 6.3 uses a percentage score by process element P1-P7). Low scores must trigger corrective action, management review input, and re-audit planning.\n\n---\n\n## Common IATF audit failures\n\n1. **CSR register not updated** when customer publishes new CSR revision\n2. **No manufacturing process audits** — only clause-based audits in the programme\n3. **Contingency plans exist but were never tested**\n4. **Temporary deviations without expiry dates** or expired deviations not closed\n5. **SC not consistently marked** across drawing, PFMEA, control plan, and work instruction\n6. **Error-proofing not tested** at every start of production (frequency not defined or records not kept)\n7. **Problem-solving procedure exists** but CARs in practice skip root cause or VOE\n\n## Output Format\n\nAt the start of each use, ask the user:\n\n> \"How would you like to receive the output?\n> **A** — Structured Markdown (formatted tables and sections, ready to copy)\n> **B** — Plain tables (simplified structure for Excel or Word)\n> **C** — Narrative report (flowing text for a formal document or email)\n>\n> Default: A.\"\n\nAdapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.\n\n## Reference files\n\n- [IATF supplemental requirements checklist](references\u002Fsupplemental-requirements.md)\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-01 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-03 | @migmcc | Added supplemental requirements reference and CSR audit coverage |\n",{"name":5,"license":15,"metadata":46,"description":7},{"author":47,"domain":48,"status":49,"created":50,"version":51,"subdomain":19,"iatf-16949":52,"industries":53,"updated_by":54,"reviewed_by":47,"last_updated":55,"standard_edition":56},"RBraga01","quality-engineering","approved","2026-06-01","1.1","9.2.2","automotive,electronics","migmcc","2026-06-03","IATF 16949:2016","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Faudit\u002Fiatf-16949-audit",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill iatf-16949-audit",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill iatf-16949-audit",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill iatf-16949-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Faudit\u002Fiatf-16949-audit\u002FSKILL.md",true,[81],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fsupplemental-requirements.md","REFERENCE","参考文档",15523,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Faudit\u002Fiatf-16949-audit\u002Freferences\u002Fsupplemental-requirements.md",[88,97,105,113,121,129],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":96},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":96},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":96},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":96},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]