checkpoint-gate

Verifies required IC design artifacts and quality thresholds before phase transitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? IC design flows risk advancing to the next phase with missing deliverables or substandard quality, causing downstream failures. This Skill enforces deterministic quality gates at each phase transition so no design proceeds without passing required file and threshold checks. ## Core Features & Use Cases - Three checkpoint gates: CP1 (Phase 1→2) validates spec documents with DS≥70 and AN≥56 scores; CP2 (Phase 2→3) checks synthesis, SVA count ≥8, and DRC ≤5; CP3 (Phase 3→Production) verifies Quartus FPGA compilation and SOF generation. - Deterministic verification: Runs checkpoint_gate_check.py to enforce fixed numeric thresholds and required-file checklists, separating programmatic checks from AI-judgment items like pin-name consistency. - Compliance auditing: Validates its own sign-off output against compliance.yaml to guarantee consistent report structure across agents. - Use Case: After completing RTL design and synthesis, run the CP2 gate to confirm the netlist, GDS, DRC report, and assertion count all meet thresholds before starting FPGA verification. ## Quick Start Ask the AI to run the checkpoint gate for the current project to verify whether the design is ready to advance to the next phase.

Frequently Asked Questions about checkpoint-gate

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

FAQPage Schema
How do I check if my IC design is ready for the next phase?▼

Run checkpoint_gate_check.py with the project directory and checkpoint number (1, 2, or 3). Exit code 0 means all required files exist and thresholds pass; exit 1 means a file is missing or a threshold is violated.

What quality thresholds does the checkpoint gate enforce?▼

CP1 requires DS score ≥70, AN score ≥56, and zero ERROR-level spec mismatches. CP2 requires synthesis pass, cell count >0, at least 8 SVA assertions, and DRC violations ≤5. CP3 requires Quartus compile success and a non-empty SOF file.

Why does checkpoint_gate_check.py fail on a healthy design?▼

The program has known path rot: it targets an abandoned directory layout (phase1_spec/ instead of phase1/generated_docs/) and fails all run trees. The SKILL.md documents this and directs agents to the per-step gate set instead.

Can the checkpoint gate replace manual design review?▼

No. The program owns numeric thresholds and file presence, but qualitative checks like pin-name consistency between datasheet and app note, register-address agreement, and STA waiver documentation still require AI or human judgment.

What are the limitations of the SVA ≥8 threshold?▼

Trivial ICs like buffers or AND gates genuinely have fewer than 8 testable properties, so the universal threshold is too strict for them. The practical notes recommend a small-IC waiver lowering the threshold to ≥4 when cell count is under 10.