formal-verification

Prove design properties and check logical equivalence in chip design.

180|46|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/chuanseng-ng/digital-chip-design-agents --skill formal-verification-chuanseng-ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formal-verification
Source: https://github.com/chuanseng-ng/digital-chip-design-agents/tree/main/plugins/formal/skills/formal-verification
Command: npx skills add https://github.com/chuanseng-ng/digital-chip-design-agents --skill formal-verification-chuanseng-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sby, yosys, boolector, z3, cadence_jaspergold, synopsys_vcf, siemens_questa_formal, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides formal property verification (FPV) and logical equivalence checking (LEC) for thorough and comprehensive verification of design properties.

Core Features & Use Cases

  • Formal Property Verification: Prove design properties exhaustively, ensuring correctness.
  • Logical Equivalence Checking: Verify RTL vs gate-level netlist equivalence.
  • CDC Verification: Formal verification of clock domain crossing issues.
  • Use Case: When you need to ensure that your design's properties are proven to hold under all possible conditions, formal verification is essential.

Quick Start

Run the formal verification skill with the command: formal-verification run --property-file path/to/properties.sv

Frequently Asked Questions about formal-verification

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

FAQPage Schema
How do I run formal property verification on my RTL design?

Logical equivalence checking verifies RTL against gate-level netlists to ensure synthesised designs match the original logic. It uses formal tools like SymbiYosys and Z3 to mathematically prove equivalence without running simulation testbenches.

Do I need commercial tools like Cadence JasperGold for CDC verification?

CDC verification can be performed using open-source tools like SymbiYosys, Boolector, and Z3, but commercial tools including Cadence JasperGold, Synopsys VCF, and Siemens Questa Formal are also supported dependencies for comprehensive clock domain crossing analysis.

What is the difference between formal verification and simulation for chip design?

Formal verification mathematically proves design properties hold under all possible conditions, while simulation tests specific test vectors. Formal methods exhaustively verify RTL correctness and logical equivalence without requiring directed or random testbenches.

Can I use SymbiYosys and Yosys for exhaustive property proving?

SymbiYosys and Yosys support exhaustive property proving for chip design by leveraging SMT solvers like Boolector and Z3. This open-source flow enables formal property verification and architectural evaluation without requiring commercial licenses.

When should I use formal verification instead of dynamic simulation?

Use formal verification when you need to ensure exhaustive correctness of design properties, RTL logic, or clock domain crossings under all conditions. It is essential when simulation cannot cover all possible state spaces or input combinations.