rtl-p5s-func-verify-policy

Define cocotb multi-seed regression policies with coverage targets and traceability output.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides a prescriptive policy and operational guidance to make Tier 3 module-level cocotb regressions consistent, traceable, and measurable so teams can reliably graduate modules to integration testing without ambiguous coverage or traceability gaps.

Core Features & Use Cases

  • Policy & Naming Conventions: Enforces cocotb signal naming, clock/reset patterns, and reset sequencing to avoid common integration failures.
  • Multi-Seed Regression & Execution Strategy: Defines a default five-seed strategy, parallelism rules, local-first execution, AWS gating, pipelined per-module execution, and early-termination thresholds.
  • Coverage & Traceability: Specifies coverage targets (line ≥ 90%, toggle ≥ 80%, FSM ≥ 70%), merging procedures, and a requirement traceability matrix format for AC-level and REQ-level reporting.
  • Use Case: Use this policy when running Phase 5 Tier 3 regressions to validate that module-level cocotb tests meet coverage targets, map failures to requirements, and produce a formal RTM for review.

Quick Start

Run the Tier 3 cocotb multi-seed regression following the policy to verify five seeds, merge coverage, and produce the requirement traceability report.

Frequently Asked Questions about rtl-p5s-func-verify-policy

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

FAQPage Schema
How do I set up cocotb multi-seed regressions for module-level RTL verification?

To set up cocotb multi-seed regressions, apply a policy enforcing a default five-seed strategy, parallelism rules, and local-first execution to validate module RTL tests with consistent seeding and reproducibility.

What coverage targets are required for RTL module verification before integration testing?

Required RTL module verification coverage targets are line coverage greater than or equal to 90%, toggle coverage greater than or equal to 80%, and FSM coverage greater than or equal to 70%, verified through merged coverage reporting.

How do I generate a requirement traceability matrix for cocotb test regressions?

Generate a requirement traceability matrix by mapping cocotb regression failures and coverage results to AC-level and REQ-level requirements, then outputting the formal RTM to reviews/phase-5-verify/requirement-traceability.md.

Does this RTL verification policy enforce cocotb signal naming and reset sequencing conventions?

Yes, the RTL verification policy enforces cocotb signal naming conventions, clock and reset patterns, and reset sequencing rules to prevent common module integration failures during regression runs.

Can I run Phase 5 Tier 3 module regressions locally and via gated cloud runners?

Yes, the verification policy supports Phase 5 Tier 3 module regressions running locally or via gated cloud runners, defining pipelined per-module execution and early-termination thresholds for optimized workflows.

Why do I need a five-seed reproducibility strategy for RTL cocotb regressions?

A five-seed reproducibility strategy is needed for RTL cocotb regressions to ensure module-level tests consistently meet coverage targets and reliably produce measurable results before graduating to integration testing.