EVT/DVT/PVT Gate Review Skill

Phase gates exist because hardware mistakes compound: an issue waved through EVT costs 10× at DVT and 100× in the field. This skill runs the gate the way a strong NPI lead does — score against written exit criteria, triage every open issue as blocker or waiver, read yield with its denominator, and make a recommendation someone can be held to.

What This Skill Produces

• A scored exit-criteria checklist for the phase under review
• An open-issue triage table (blocker / waiver / defer) with rationale
• A yield readout by test station with failure Pareto
• A waiver register with class, owner, expiry, and containment
• A go / conditional-go / no-go recommendation with the conditions written down

Required Inputs

Ask for these if not provided; run the review on partial data but mark unverifiable criteria [no data — cannot score], never assumed-pass:

• Which gate — EVT, DVT, or PVT exit (or entry to the next phase)
• Build results — units built, units passing, failures by test station or symptom
• Open issue list — bugs/defects with severity and status
• Exit criteria if the program has them; otherwise use the reference set below and say so
• Schedule pressure — the real next-build date, so the recommendation is honest about trade-offs

Gate Framework

Reference exit criteria (adapt to the program's own if provided):

Criterion	EVT exit	DVT exit	PVT exit
Proves	Design works (works-like)	Design is reliable & certifiable (looks-like/works-like)	Factory can build it at rate
Tooling	Proto/soft tooling OK	Off near-final tooling	Production tooling, production line
Functional yield	≥ ~80% with failures understood	≥ ~90%