rtl-p5s-cdc-verify

Analyzes clock domain crossings and generates CDC reports plus SDC constraint files.

43|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-p5s-cdc-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rtl-p5s-cdc-verify
Source: https://github.com/babyworm/rtl-agent-team/tree/main/skills/rtl-p5s-cdc-verify
Command: npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-p5s-cdc-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many multi-clock RTL designs suffer from undetected clock domain crossing (CDC) bugs such as missing synchronizers, improper multi-bit transfers, and reconvergence issues that lead to intermittent metastability and silicon failures. This Skill provides a structured, static-analysis-driven approach to detect those risks early and produce actionable remediation guidance.

Core Features & Use Cases

  • Perform structural CDC analysis to map registers to clock domains and enumerate cross-domain signals.
  • Verify synchronizer patterns (2-FF, 3-FF, gray-code, handshake, async FIFO) and flag Violations/Cautions with explanations and remediation steps.
  • Generate human-readable CDC reports and SDC constraint files for signoff and downstream EDA tools; useful during pre-synthesis sign-off, new clock domain additions, or CDC checklist audits.

Quick Start

Run CDC verification on the top module to produce a CDC analysis report and corresponding SDC constraints.

Frequently Asked Questions about rtl-p5s-cdc-verify

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

FAQPage Schema
How do I find missing synchronizers in multi-clock RTL during verification?

To find missing synchronizers in multi-clock RTL, static CDC analysis maps registers to clock domains and enumerates cross-domain signals to flag metastability risks and structural violations. This verifies synchronizer patterns and highlights gaps during pre-synthesis sign-off.

Can I generate SDC constraints from clock domain crossing analysis?

Yes, you can generate SDC constraints from clock domain crossing analysis by assessing synchronizer quality and identifying CDC constraint gaps. The analysis produces SDC constraint files for downstream EDA tools alongside human-readable markdown reports.

What clock domain crossing risks should I check before pre-synthesis sign-off?

Before pre-synthesis sign-off, check clock domain crossing risks including missing synchronizers, improper multi-bit transfers, and reconvergence issues. Static analysis identifies these metastability risks and verifies synchronizer patterns like 2-FF, gray-code, and async FIFO.

How do I verify synchronizer patterns and reconvergence in RTL?

To verify synchronizer patterns and reconvergence in RTL, static analysis evaluates multi-clock domain crossings against known patterns like 2-FF, 3-FF, and handshake synchronizers. It flags violations or cautions with explanations and remediation steps.

Does CDC static analysis work without external verification dependencies?

Yes, CDC static analysis works without external verification dependencies. It structurally analyzes the RTL source to map registers to domains, enumerate crossings, and generate CDC reports plus SDC constraints using only the provided design files.