Individual skill

dfmea-design

Build a design risk analysis, DFMEA worksheet, or interface analysis using the AIAG-VDA FMEA Handbook 2019. Covers design intent, interface failures, boundary diagram, and design robustness before manufacturing. Use during new product development, design changes, or when a field failure reveals a design weakness. Required for IATF 16949 §8.3 scope.

plugins/RBraga01/Quality-Engineering-Skills/skills/risk-analysis/dfmea-design/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Design FMEA (DFMEA) — AIAG-VDA 2019

## Goal

Identify and mitigate design risks by analysing functions, interfaces, and failure modes — so that design weaknesses are resolved before release to manufacturing, and the results feed directly into the DVP, PFMEA, and Control Plan.

## Required Execution Checklist

- [ ] DFMEA scope defined: boundary diagram complete, inside/outside boundary identified
- [ ] Product hierarchy mapped: system → subsystem → component → interface (Step 2)
- [ ] All interfaces identified — internal (component-to-component), external (environment), and user/assembly
- [ ] All functions defined with Verb + Noun + Measurable Standard (Step 3)
- [ ] Each function has a measurable verification method confirmed in the DVP
- [ ] Failure chain complete: Effect → Mode → Cause for each function (Step 4)