rtl-p5-verify-policy

Codify Phase 5 verification governance for RTL designs with graduation gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 5 verification governance for RTL designs, defining module graduation gates, coverage targets, and synthesis estimation rules to standardize verification effort and timelines.

Core Features & Use Cases

  • Defines a three-stage Phase 5 verification architecture (Stage 1: per-module checks, Stage 2: top-level integration, Stage 3: final compliance) to streamline risk management and scheduling.
  • Specifies concrete graduation gates for V1 through V9 checks, including lint, formal verification, CDC, protocol, functional regression, coverage, performance, synthesis estimation, and code review.
  • Guides continuous improvement with defect feedback loops, escalation paths, and traceability artifacts to support audit-ready verification.

Quick Start

Follow this policy to align your module verification plan with Phase 5 gates and targets.

Frequently Asked Questions about rtl-p5-verify-policy

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

FAQPage Schema
What are the standard RTL verification graduation gates for module sign-off?

Standard RTL verification graduation gates include V1 through V9 checks: lint, formal verification, CDC, protocol, functional regression, coverage, performance, synthesis estimation, and code review to standardize verification effort.

How do I structure a multi-stage RTL verification plan for top-level integration?

Structure RTL verification across three stages: Stage 1 for per-module checks, Stage 2 for top-level integration, and Stage 3 for final post-silicon compliance to streamline risk management and scheduling.

When do I need to enforce formal verification and CDC checks in RTL design?

You need to enforce formal verification and CDC checks during Stage 1 per-module graduation gates to standardize verification timelines and ensure audit-ready traceability artifacts for multi-module projects.

Does this RTL verification policy support continuous improvement and defect tracking?

Yes, the RTL verification policy guides continuous improvement by defining defect feedback loops, escalation paths, and traceability artifacts to support audit-ready verification across all modules.

What is the best way to standardize RTL verification effort and timelines across modules?

The best way to standardize RTL verification effort is to codify Phase 5 verification governance, defining module graduation gates, coverage targets, and synthesis estimation rules for consistent scheduling.

How does synthesis estimation fit into the Phase 5 RTL verification gates?

Synthesis estimation serves as the V8 check within Phase 5 RTL verification gates, acting as a criteria for Stage 1-3 progression to ensure designs meet expected performance and compliance metrics.