analog-output-verify

Verifies analog design A1-A9 outputs against deterministic gates and AI judgment checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analog design automation can mark steps PASS or WAIVED without confirming real correctness, since analog quality is rarely binary. This Skill closes that gap by spot-checking corner-simulation coverage, hardmacro completeness, and hardware-vs-SPICE data fidelity after the analog one-shot runner finishes. ## Core Features & Use Cases - Deterministic gate orchestration: Runs per-step checker programs for A3 netlists, A4 corner sweeps, A5 layouts, A6 per-block DRC/LVS, A7 post-layout resim, A8 hardmacro LEF/GDS outlines, and A9 hardware correlation. - AI judgment layer: Applies residual checks programs cannot make, such as silicon-realistic specs, topology-to-spec consistency, and outlier patterns in corner data. - Escalation routing: Directs failures to the right follow-up loop, such as analog-sizing-loop for corner failures or analog-hw-tuning-loop for hardware correlation drift. - Use Case: After /vibe-ic-analog reports PASS on an amplifier block, run this Skill to confirm the 9-corner sweep has real margins, the LEF outline matches the GDS bounding box, and HW-vs-SPICE error stays under 5%. ## Quick Start Ask the AI to review the analog outputs of the current project and verify the A4 corner sweep and A8 hardmacro results.

Frequently Asked Questions about analog-output-verify

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

FAQPage Schema
How do I verify analog corner simulation results?▼

Run the A4 corner sweep checker programs against the project, which enforce anti-stub rules, simulator provenance, worst-corner margin, and the 9-corner floor of 3 process by 3 temperature points. Then eyeball the corner data for systematic offsets the numeric gates pass.

How to check that an analog hardmacro is complete?▼

The A8 gate verifies LEF, liberty, GDS, and Verilog files are present and non-stub, and a separate outline checker confirms the LEF SIZE statement matches the GDS bounding box numerically. A mismatch or missing half produces an honest FAIL.

What does WAIVED mean in the analog A1-A9 flow?▼

WAIVED means the step needs human or domain-skill attention rather than being a clean pass. Even PASS steps still need verification because analog correctness is rarely binary, which is what this verification skill provides.

When should analog verification escalate to a sizing or tuning loop?▼

Escalate to analog-sizing-loop when the A4 corner check fails, to analog-extraction-resim when post-layout versus pre-layout degradation exceeds 30 percent, and to analog-hw-tuning-loop when hardware versus SPICE error exceeds 15 percent.

Why did the A5 layout check fail even though DRC and LVS are clean?▼

A5 only checks that layout.mag or GDS files exist with real placed geometry for every declared block. DRC and LVS sign-off belong to A6, so partial block coverage marks A5 as INCOMPLETE regardless of DRC/LVS status.