rtl-p5s-perf-policy

Enforce RTL performance verification rules with naming conventions and BFM thresholds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and enforces consistent performance verification across RTL projects, including naming conventions, threshold checks, and validation procedures.

Core Features & Use Cases

  • Performance Monitor Naming Conventions: enforces i_ and o_ prefixes, proper clk and rst naming, and u_ prefix for performance counters.
  • Escalation & Stop Conditions: defines thresholds and escalation paths for pipeline analysis and verification halts.
  • Final Checklist: provides a structured checklist to ensure deterministic verification across modules.
  • Stress Vector Patterns: prescribes stress vectors and timing patterns for cycle-accurate measurement.

Quick Start

Review the Performance Verification Policy and apply its conventions to your RTL testbenches immediately.

Frequently Asked Questions about rtl-p5s-perf-policy

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

FAQPage Schema
What are standard naming conventions for RTL performance verification testbenches?

Standard RTL performance verification enforces i_ and o_ prefixes for ports, proper clk and rst naming, and u_ prefix for performance counters to ensure naming consistency across modules.

How do I define stop conditions and escalation paths for RTL verification workflows?

Define RTL verification stop conditions and escalation paths by setting specific BFM thresholds for pipeline analysis, ensuring deterministic verification halts when performance metrics breach baseline limits.

What stress vector patterns are used for cycle-accurate RTL performance measurement?

Cycle-accurate RTL performance measurement uses prescribed stress vector patterns and timing patterns to validate performance monitors against the BFM baseline during testbench verification workflows.

How do I apply a performance verification checklist to ensure deterministic RTL design verification?

Apply a structured final checklist to your RTL design verification workflow to validate naming conventions, metric definitions, and verifiable test vectors, ensuring deterministic verification across project stages.

When should I use standardized performance verification policies for RTL projects?

Use standardized performance verification policies for RTL projects when you need consistent BFM threshold checks, naming consistency, and verifiable test vectors validated against stress vectors across all design verification stages.