[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD9XE3NN2DX06Y989NP68K":3,"skill-same:01M6MD9XE3NN2DX06Y989NP68K":95},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6MD9XE3NN2DX06Y989NP68K","pfmea-process",null,"Build a PFMEA worksheet, process risk analysis, or AP table using the AIAG-VDA FMEA Handbook 2019 7-step approach. Covers Structure Analysis, Function Analysis, Failure Analysis, Risk Analysis (Action Priority H\u002FM\u002FL), Optimization, and Documentation. Required by IATF 16949 and OEM customer-specific requirements for new processes, process changes, and post-escape PFMEA updates.","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\u002Frisk-analysis\u002Fpfmea-process\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"pfmea process","process","requirements","new","2026","automotive","handbook","for","updates","action","failure analysis","electronics","medical","customer","structure","general","oem","table","analysis","risk-analysis","risk","Optimization","documentation","2026-11-10 10:12:30",false,"---\nname: pfmea-process\ndescription: >-\n  Build a PFMEA worksheet, process risk analysis, or AP table using the AIAG-VDA FMEA\n  Handbook 2019 7-step approach. Covers Structure Analysis, Function Analysis, Failure\n  Analysis, Risk Analysis (Action Priority H\u002FM\u002FL), Optimization, and Documentation.\n  Required by IATF 16949 and OEM customer-specific requirements for new processes,\n  process changes, and post-escape PFMEA updates.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"8.1\"\n  iatf-16949: \"8.3.3.3\"\n  aiag-reference: \"AIAG-VDA FMEA Handbook 2019, Steps 1–7\"\n  domain: quality-engineering\n  subdomain: risk-analysis\n  industries: automotive,electronics,aerospace,medical,general\n  status: approved\n  created: \"2026-06-01\"\n  last_updated: \"2026-06-03\"\n  updated_by: RBraga01\n  reviewed_by: RBraga01\n  standard_edition: \"AIAG-VDA FMEA Handbook 2019\"\n---\n\n# Process FMEA (PFMEA) — AIAG-VDA 2019\n\n## Goal\n\nIdentify and prioritise process risk before production — using the AIAG-VDA 2019 7-step approach — so that high-priority failure modes are eliminated or controlled before they reach the customer, and the result feeds directly into the Control Plan and Work Instructions.\n\n## Required Execution Checklist\n\n- [ ] Scope defined: process step boundaries, model year, team assembled with cross-functional representation\n- [ ] Process Flow Diagram (PFD) available and used as Step 2 input\n- [ ] All process steps in the PFD have a corresponding entry in Structure Analysis (Step 2)\n- [ ] Every process step has at least one Function defined in Step 3\n- [ ] Failure chain complete for each function: Effect → Mode → Cause (in this direction — not reversed)\n- [ ] All Failure Causes are evidence-based — no unverified assumptions used as final causes\n- [ ] S\u002FO\u002FD ratings agreed by the cross-functional team and documented\n- [ ] All Special Characteristics have S=9 or S=10\n- [ ] Every H-AP item has a named owner, target date, and is tracked to closure\n- [ ] PFMEA detection controls match the Control Plan; prevention controls match Work Instructions\n\n---\n\n## When to use\n\n- New process development (pre-production)\n- Existing process change or transfer\n- After a quality escape (update to reflect failure mode)\n- Periodic review (IATF requires annual review or at change)\n- Customer-specific requirement (Ford, GM, Stellantis, BMW, VW all require PFMEA)\n\n## Prerequisites\n\n- Process flow diagram (PFD) — required for Step 2\n- Product drawings with special characteristics identified\n- DFMEA (if applicable) for effect severity reference\n- Team: process engineer, quality engineer, production supervisor, maintenance\n\n## The 7-Step AIAG-VDA 2019 Approach\n\n---\n\n### Step 1 — Planning and Preparation\n\nDefine the scope:\n- **FMEA header:** part number, part name, model year, process step scope, revision, date, team\n- **Analysis boundary:** which process steps are in scope (start point and end point)\n- **Timeline:** new PFMEA or revision of existing?\n\nPrepare:\n- Process Flow Diagram (PFD) — this drives Steps 2 and 3\n- List of Special Characteristics (SC) from the drawing (symbols: ◆ ★ ⬟ vary by customer)\n\n---\n\n### Step 2 — Structure Analysis\n\nMap the process hierarchy:\n```\nProcess Item (e.g., Steering Column Assembly Line)\n└── Process Step (e.g., Station 3 — Torque tightening)\n    └── Work Element (e.g., Pneumatic driver, torque wrench)\n```\n\nFor each process step, identify the **4M inputs**: Man, Machine, Method, Material.\n\nThis structure becomes the \"what can go wrong\" framework in Step 4.\n\n**Consistency check:** Every Process Step defined here must have at least one Function defined in Step 3. A process step with no function is incomplete — it cannot be analysed for failure in Step 4.\n\n---\n\n### Step 3 — Function Analysis\n\nFor each process step and work element, define:\n- **Process function:** what should happen? (verb + noun + measurable characteristic)\n  - Example: \"Tighten bolt M8 to 22 ± 2 Nm\"\n- **Product characteristic:** what product feature results from this step?\n  - Flag all Special Characteristics (SC) — these get highest attention in D\u002FO\u002FD ratings\n\n**Functional chain:**\n```\nWork Element function → Process Step function → Product Characteristic\n(tool applies torque) → (bolt is tightened to spec) → (joint meets strength requirement)\n```\n\n---\n\n### Step 4 — Failure Analysis\n\nFor each function, identify the failure chain: **Failure Effect → Failure Mode → Failure Cause**\n\nWork in this direction (Effect first, then Mode, then Cause):\n\n**Failure Effect (FE):** what is the impact on the customer (internal or end user)?\n- End-user effect (most severe): safety, regulatory non-compliance, loss of function\n- Manufacturing effect: rework, scrap, line stoppage, warranty\n\n**Failure Mode (FM):** how does this process step fail to perform its function?\n- Example: \"Bolt torqued too low\", \"Part installed backwards\", \"Incorrect material loaded\"\n\n**Failure Cause (FC):** what causes the failure mode?\n- Machine: \"Torque wrench not calibrated\", \"Air pressure drop\"\n- Man: \"Work instruction not followed\", \"Untrained operator\"\n- Method: \"Incorrect torque value in WI\", \"No torque verification step\"\n- Material: \"Wrong bolt grade loaded\", \"Lubrication not applied\"\n\n**Multiple causes per failure mode are normal** — each FC gets its own row.\n\n**Failure Cause validation:** Failure Causes must be supported by objective evidence or structured root cause analysis (e.g., [5-Why](..\u002F..\u002Fproblem-solving\u002F5why-root-cause\u002F)). Unverified assumptions — \"probably,\" \"may be,\" \"could be\" — must not be entered as final Failure Causes. For post-escape PFMEA updates, the FC must match the validated root cause from the 8D or CAPA, not a revised opinion.\n\n---\n\n### Step 5 — Risk Analysis (Action Priority)\n\nFor each FC row, assign three ratings:\n\n#### Severity (S) — impact of the Failure Effect on the customer\n\n| S | Effect |\n|---|--------|\n| 10 | Safety — affects operator safety without warning |\n| 9 | Regulatory non-compliance |\n| 8 | Loss of primary function (end user) |\n| 7 | Reduced primary function |\n| 6 | Loss of comfort \u002F convenience function |\n| 5 | Reduced comfort \u002F convenience function |\n| 4 | Appearance issue — noticed by most |\n| 3 | Appearance issue — noticed by some |\n| 2 | Appearance issue — noticed by discriminating |\n| 1 | No effect |\n\n**Severity rates the EFFECT, not the mode or cause.** S=10 or S=9 means you must act regardless of O and D.\n\n#### Occurrence (O) — likelihood the Failure Cause leads to the Failure Mode\n\n| O | Failure Rate |\n|---|-------------|\n| 10 | ≥ 1 in 2 |\n| 9 | 1 in 8 |\n| 8 | 1 in 20 |\n| 7 | 1 in 80 |\n| 6 | 1 in 400 |\n| 5 | 1 in 2,000 |\n| 4 | 1 in 15,000 |\n| 3 | 1 in 150,000 |\n| 2 | 1 in 1,500,000 |\n| 1 | Failure eliminated by prevention control |\n\nO considers **prevention controls** already in place (poka-yoke, SPC, incoming inspection of material).\n\n#### Detection (D) — effectiveness of detection controls before product reaches next customer\n\n| D | Detection |\n|---|-----------|\n| 10 | No detection control |\n| 9 | Control unlikely to detect |\n| 8 | Control may detect |\n| 7 | Control has low chance of detection |\n| 6 | Control may detect — moderate |\n| 5 | Control likely to detect |\n| 4 | Control has good chance of detection |\n| 3 | Control almost certain to detect |\n| 2 | Control certain to detect — automatic rejection |\n| 1 | Failure mode cannot occur (prevented) |\n\nD considers **detection controls** already in place (gauging, inspection, poka-yoke).\n\n#### Action Priority (AP) — replaces legacy RPN\n\nUse the AP table (see [action-priority-ap](..\u002Faction-priority-ap\u002F) skill for full table):\n\n| AP | Meaning | Required action |\n|----|---------|-----------------|\n| **H** (High) | Action required | Assign responsible owner + target date. Escalate if no improvement possible. |\n| **M** (Medium) | Action recommended | Team should evaluate — reduction may be beneficial |\n| **L** (Low) | No action required | Document rationale for no action |\n\n**Critical rule:** S = 9 or 10 → AP is always H regardless of O and D.\n\n**Ratings discipline:** All S\u002FO\u002FD ratings must be agreed by the cross-functional team — not assigned unilaterally by one engineer. Where team members disagree, document the rationale for the rating chosen. Ratings without team consensus are not acceptable for PPAP submission or customer OEM review.\n\n---\n\n### Step 6 — Optimization\n\nFor every H-AP item: define a corrective action.\n\nFor each action:\n- Description of the action\n- Responsible person (name, not function)\n- Target completion date\n- Re-assess S\u002FO\u002FD after action: new AP (revised)\n\n**Priority for action type:**\n1. **Prevent the cause** (best): eliminate the cause by design or poka-yoke\n2. **Reduce occurrence**: add process control that makes the cause less likely\n3. **Improve detection**: add or improve detection control (least preferred — doesn't prevent defect, only catches it)\n\nAvoid the common trap of only improving detection (lowering D) — this catches defects but doesn't prevent them.\n\n**Tracking discipline:** All actions must be logged in the PFMEA and tracked to closure with objective evidence (completed action description + implementation date + revised S\u002FO\u002FD ratings). Open H-AP items past their target date must be escalated to management with a documented reason for delay and a revised target date. A PFMEA with overdue open H-AP items is not acceptable for PPAP submission or OEM audit.\n\n---\n\n### Step 7 — Results Documentation\n\nFinal PFMEA deliverables:\n- Completed PFMEA form with all 7 steps documented\n- Summary of H-AP items and their actions (status: open\u002Fclosed)\n- Link to updated Control Plan (detection controls in PFMEA → control methods in CP)\n- Link to updated Work Instructions (prevention controls → WI procedures)\n- PFMEA revision history\n\n**PFMEA → Control Plan linkage:**\nEvery detection control in the PFMEA must have a corresponding entry in the Control Plan. Every prevention control must be reflected in the Work Instruction.\n\n## Validation checklist\n\nBefore releasing the PFMEA:\n- [ ] All process steps from the PFD are in the Structure Analysis\n- [ ] All Special Characteristics are identified and have S=9 or S=10\n- [ ] Every H-AP item has an owner and a target date\n- [ ] No H-AP items remain open without documented escalation reason\n- [ ] Detection controls in PFMEA match the Control Plan\n- [ ] Prevention controls in PFMEA match Work Instructions\n- [ ] All Failure Causes are evidence-based (no unverified assumptions used as final causes)\n- [ ] PFMEA review triggered by one of the mandatory events: process change, quality escape (post-8D update), or annual review (IATF 16949 §8.3.3.3)\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- [AIAG-VDA 2019 step-by-step guide](references\u002Faiag-vda-2019.md)\n- [Action Priority table](assets\u002Fap-table.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 | @RBraga01 | Expanded 7-step workflow with AP gate requirements and PPAP integration |\n","# Process FMEA (PFMEA) — AIAG-VDA 2019\n\n## Goal\n\nIdentify and prioritise process risk before production — using the AIAG-VDA 2019 7-step approach — so that high-priority failure modes are eliminated or controlled before they reach the customer, and the result feeds directly into the Control Plan and Work Instructions.\n\n## Required Execution Checklist\n\n- [ ] Scope defined: process step boundaries, model year, team assembled with cross-functional representation\n- [ ] Process Flow Diagram (PFD) available and used as Step 2 input\n- [ ] All process steps in the PFD have a corresponding entry in Structure Analysis (Step 2)\n- [ ] Every process step has at least one Function defined in Step 3\n- [ ] Failure chain complete for each function: Effect → Mode → Cause (in this direction — not reversed)\n- [ ] All Failure Causes are evidence-based — no unverified assumptions used as final causes\n- [ ] S\u002FO\u002FD ratings agreed by the cross-functional team and documented\n- [ ] All Special Characteristics have S=9 or S=10\n- [ ] Every H-AP item has a named owner, target date, and is tracked to closure\n- [ ] PFMEA detection controls match the Control Plan; prevention controls match Work Instructions\n\n---\n\n## When to use\n\n- New process development (pre-production)\n- Existing process change or transfer\n- After a quality escape (update to reflect failure mode)\n- Periodic review (IATF requires annual review or at change)\n- Customer-specific requirement (Ford, GM, Stellantis, BMW, VW all require PFMEA)\n\n## Prerequisites\n\n- Process flow diagram (PFD) — required for Step 2\n- Product drawings with special characteristics identified\n- DFMEA (if applicable) for effect severity reference\n- Team: process engineer, quality engineer, production supervisor, maintenance\n\n## The 7-Step AIAG-VDA 2019 Approach\n\n---\n\n### Step 1 — Planning and Preparation\n\nDefine the scope:\n- **FMEA header:** part number, part name, model year, process step scope, revision, date, team\n- **Analysis boundary:** which process steps are in scope (start point and end point)\n- **Timeline:** new PFMEA or revision of existing?\n\nPrepare:\n- Process Flow Diagram (PFD) — this drives Steps 2 and 3\n- List of Special Characteristics (SC) from the drawing (symbols: ◆ ★ ⬟ vary by customer)\n\n---\n\n### Step 2 — Structure Analysis\n\nMap the process hierarchy:\n```\nProcess Item (e.g., Steering Column Assembly Line)\n└── Process Step (e.g., Station 3 — Torque tightening)\n    └── Work Element (e.g., Pneumatic driver, torque wrench)\n```\n\nFor each process step, identify the **4M inputs**: Man, Machine, Method, Material.\n\nThis structure becomes the \"what can go wrong\" framework in Step 4.\n\n**Consistency check:** Every Process Step defined here must have at least one Function defined in Step 3. A process step with no function is incomplete — it cannot be analysed for failure in Step 4.\n\n---\n\n### Step 3 — Function Analysis\n\nFor each process step and work element, define:\n- **Process function:** what should happen? (verb + noun + measurable characteristic)\n  - Example: \"Tighten bolt M8 to 22 ± 2 Nm\"\n- **Product characteristic:** what product feature results from this step?\n  - Flag all Special Characteristics (SC) — these get highest attention in D\u002FO\u002FD ratings\n\n**Functional chain:**\n```\nWork Element function → Process Step function → Product Characteristic\n(tool applies torque) → (bolt is tightened to spec) → (joint meets strength requirement)\n```\n\n---\n\n### Step 4 — Failure Analysis\n\nFor each function, identify the failure chain: **Failure Effect → Failure Mode → Failure Cause**\n\nWork in this direction (Effect first, then Mode, then Cause):\n\n**Failure Effect (FE):** what is the impact on the customer (internal or end user)?\n- End-user effect (most severe): safety, regulatory non-compliance, loss of function\n- Manufacturing effect: rework, scrap, line stoppage, warranty\n\n**Failure Mode (FM):** how does this process step fail to perform its function?\n- Example: \"Bolt torqued too low\", \"Part installed backwards\", \"Incorrect material loaded\"\n\n**Failure Cause (FC):** what causes the failure mode?\n- Machine: \"Torque wrench not calibrated\", \"Air pressure drop\"\n- Man: \"Work instruction not followed\", \"Untrained operator\"\n- Method: \"Incorrect torque value in WI\", \"No torque verification step\"\n- Material: \"Wrong bolt grade loaded\", \"Lubrication not applied\"\n\n**Multiple causes per failure mode are normal** — each FC gets its own row.\n\n**Failure Cause validation:** Failure Causes must be supported by objective evidence or structured root cause analysis (e.g., [5-Why](..\u002F..\u002Fproblem-solving\u002F5why-root-cause\u002F)). Unverified assumptions — \"probably,\" \"may be,\" \"could be\" — must not be entered as final Failure Causes. For post-escape PFMEA updates, the FC must match the validated root cause from the 8D or CAPA, not a revised opinion.\n\n---\n\n### Step 5 — Risk Analysis (Action Priority)\n\nFor each FC row, assign three ratings:\n\n#### Severity (S) — impact of the Failure Effect on the customer\n\n| S | Effect |\n|---|--------|\n| 10 | Safety — affects operator safety without warning |\n| 9 | Regulatory non-compliance |\n| 8 | Loss of primary function (end user) |\n| 7 | Reduced primary function |\n| 6 | Loss of comfort \u002F convenience function |\n| 5 | Reduced comfort \u002F convenience function |\n| 4 | Appearance issue — noticed by most |\n| 3 | Appearance issue — noticed by some |\n| 2 | Appearance issue — noticed by discriminating |\n| 1 | No effect |\n\n**Severity rates the EFFECT, not the mode or cause.** S=10 or S=9 means you must act regardless of O and D.\n\n#### Occurrence (O) — likelihood the Failure Cause leads to the Failure Mode\n\n| O | Failure Rate |\n|---|-------------|\n| 10 | ≥ 1 in 2 |\n| 9 | 1 in 8 |\n| 8 | 1 in 20 |\n| 7 | 1 in 80 |\n| 6 | 1 in 400 |\n| 5 | 1 in 2,000 |\n| 4 | 1 in 15,000 |\n| 3 | 1 in 150,000 |\n| 2 | 1 in 1,500,000 |\n| 1 | Failure eliminated by prevention control |\n\nO considers **prevention controls** already in place (poka-yoke, SPC, incoming inspection of material).\n\n#### Detection (D) — effectiveness of detection controls before product reaches next customer\n\n| D | Detection |\n|---|-----------|\n| 10 | No detection control |\n| 9 | Control unlikely to detect |\n| 8 | Control may detect |\n| 7 | Control has low chance of detection |\n| 6 | Control may detect — moderate |\n| 5 | Control likely to detect |\n| 4 | Control has good chance of detection |\n| 3 | Control almost certain to detect |\n| 2 | Control certain to detect — automatic rejection |\n| 1 | Failure mode cannot occur (prevented) |\n\nD considers **detection controls** already in place (gauging, inspection, poka-yoke).\n\n#### Action Priority (AP) — replaces legacy RPN\n\nUse the AP table (see [action-priority-ap](..\u002Faction-priority-ap\u002F) skill for full table):\n\n| AP | Meaning | Required action |\n|----|---------|-----------------|\n| **H** (High) | Action required | Assign responsible owner + target date. Escalate if no improvement possible. |\n| **M** (Medium) | Action recommended | Team should evaluate — reduction may be beneficial |\n| **L** (Low) | No action required | Document rationale for no action |\n\n**Critical rule:** S = 9 or 10 → AP is always H regardless of O and D.\n\n**Ratings discipline:** All S\u002FO\u002FD ratings must be agreed by the cross-functional team — not assigned unilaterally by one engineer. Where team members disagree, document the rationale for the rating chosen. Ratings without team consensus are not acceptable for PPAP submission or customer OEM review.\n\n---\n\n### Step 6 — Optimization\n\nFor every H-AP item: define a corrective action.\n\nFor each action:\n- Description of the action\n- Responsible person (name, not function)\n- Target completion date\n- Re-assess S\u002FO\u002FD after action: new AP (revised)\n\n**Priority for action type:**\n1. **Prevent the cause** (best): eliminate the cause by design or poka-yoke\n2. **Reduce occurrence**: add process control that makes the cause less likely\n3. **Improve detection**: add or improve detection control (least preferred — doesn't prevent defect, only catches it)\n\nAvoid the common trap of only improving detection (lowering D) — this catches defects but doesn't prevent them.\n\n**Tracking discipline:** All actions must be logged in the PFMEA and tracked to closure with objective evidence (completed action description + implementation date + revised S\u002FO\u002FD ratings). Open H-AP items past their target date must be escalated to management with a documented reason for delay and a revised target date. A PFMEA with overdue open H-AP items is not acceptable for PPAP submission or OEM audit.\n\n---\n\n### Step 7 — Results Documentation\n\nFinal PFMEA deliverables:\n- Completed PFMEA form with all 7 steps documented\n- Summary of H-AP items and their actions (status: open\u002Fclosed)\n- Link to updated Control Plan (detection controls in PFMEA → control methods in CP)\n- Link to updated Work Instructions (prevention controls → WI procedures)\n- PFMEA revision history\n\n**PFMEA → Control Plan linkage:**\nEvery detection control in the PFMEA must have a corresponding entry in the Control Plan. Every prevention control must be reflected in the Work Instruction.\n\n## Validation checklist\n\nBefore releasing the PFMEA:\n- [ ] All process steps from the PFD are in the Structure Analysis\n- [ ] All Special Characteristics are identified and have S=9 or S=10\n- [ ] Every H-AP item has an owner and a target date\n- [ ] No H-AP items remain open without documented escalation reason\n- [ ] Detection controls in PFMEA match the Control Plan\n- [ ] Prevention controls in PFMEA match Work Instructions\n- [ ] All Failure Causes are evidence-based (no unverified assumptions used as final causes)\n- [ ] PFMEA review triggered by one of the mandatory events: process change, quality escape (post-8D update), or annual review (IATF 16949 §8.3.3.3)\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- [AIAG-VDA 2019 step-by-step guide](references\u002Faiag-vda-2019.md)\n- [Action Priority table](assets\u002Fap-table.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 | @RBraga01 | Expanded 7-step workflow with AP gate requirements and PPAP integration |\n",{"name":5,"license":15,"metadata":47,"description":7},{"author":48,"domain":49,"status":50,"created":51,"version":52,"iso-9001":53,"subdomain":38,"iatf-16949":54,"industries":55,"updated_by":48,"reviewed_by":48,"last_updated":56,"aiag-reference":57,"standard_edition":58},"RBraga01","quality-engineering","approved","2026-06-01","1.1","8.1","8.3.3.3","automotive,electronics,aerospace,medical,general","2026-06-03","AIAG-VDA FMEA Handbook 2019, Steps 1–7","AIAG-VDA FMEA Handbook 2019","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fpfmea-process",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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill pfmea-process",{"tool":75,"command":76},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill pfmea-process",{"tool":78,"command":79},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill pfmea-process","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fpfmea-process\u002FSKILL.md",true,[83,89],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Fap-table.md","ASSET","资产文件",3258,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fpfmea-process\u002Fassets\u002Fap-table.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Faiag-vda-2019.md","REFERENCE","参考文档",15569,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Frisk-analysis\u002Fpfmea-process\u002Freferences\u002Faiag-vda-2019.md",[96,105,113,121,129,137],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":104},"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":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":104},"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":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":104},"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":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":104},"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":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":104},"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":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":104},"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",[],[]]