tapeout-checklist

Validates DRC, LVS, STA, IR-drop, EM, and DFT signoff status before GDS tape-out release.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill tapeout-checklist-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tapeout-checklist
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/tapeout-checklist
Command: npx skills add https://github.com/vibeic/vibe-ic --skill tapeout-checklist-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tape-out is a one-way door: shipping a GDS with an unverified signoff item means a failed fabrication run. This Skill runs the final pre-tapeout gate, confirming every signoff category is green or covered by a documented, human-approved waiver before GDS hand-off. ## Core Features & Use Cases - Deterministic signoff gating: Runs flow_compliance_check, tapeout_checklist_gen, signoff_audit, and foundry signoff programs, refusing to declare tape-out readiness if any returns FAIL. - Eight-category checklist: Covers functional, timing, power integrity (IR-drop/EM), physical (DRC/LVS/antenna/density/ERC), DFT coverage, power intent, documentation, and GDS release with per-item status. - Waiver governance: Validates waiver schema and honesty (no AI self-approval), then assesses residual risk for each deferred item. - Use Case: Two weeks before a shuttle deadline, run the checklist to discover LVS is clean but IR-drop exceeds the 10% Vdd budget, route that red item to the IR-drop triage skill, and produce a go/no-go report with waivers enumerated. ## Quick Start Run the tapeout checklist on my project directory and tell me whether the design is ready for GDS release.

Frequently Asked Questions about tapeout-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my chip design is ready for tape-out?▼

Run the mandatory preflight programs: flow_compliance_check in strict mode, tapeout_checklist_gen, signoff_audit, and the foundry signoff plan check. Tape-out readiness requires all to return PASS, or PASS_WITH_WAIVERS with every waiver documented and human-approved.

What signoff checks are required before GDS release?▼

The checklist covers eight categories: functional (regression, formal, LEC), timing (MCMM STA), power integrity (IR-drop, EM), physical (DRC, LVS, antenna, density, ERC), DFT coverage, power intent (UPF), documentation, and GDS release with checksum.

Can I tape out with waivers on some signoff checks?▼

A PASS_WITH_WAIVERS verdict means structurally complete but with deferred steps, which is not tape-out ready in the foundry sense. Each waiver needs an ID, reason, ticket, and a named human approver; AI or self-approval is rejected by the waiver gate.

Why does comparing two GDS files by md5 always show a difference?▼

GDSII stream-out stamps write timestamps into BGNLIB and BGNSTR records, so two stream-outs of one layout are never byte-equal. Use gds_canonical_digest.py, which zeroes those date fields before hashing, to compare layout content across runs.

What DFT coverage is required for tape-out signoff?▼

Scan ATPG stuck-at coverage must meet the foundry floor of 95% (up to 98%), and a missing DFT report is a FAIL, not a skip. Transition at-speed coverage must meet target or carry a documented open-source tool limitation, and padded designs need boundary-scan BSDL.