rtl-p5s-integration-test-policy

Define Tier 4 integration test ordering and JSON result schemas for RTL pipelines.

43|9|Updated Feb 25, 2026

Search Tags:#testing #integration #verification #simulation #policy #rtl #tier4

Ready to run

npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-p5s-integration-test-policy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rtl-p5s-integration-test-policy
Source: https://github.com/babyworm/rtl-agent-team/tree/main/skills/rtl-p5s-integration-test-policy
Command: npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-p5s-integration-test-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integration test policy that standardizes Tier 4 integration testing practices for RTL design pipelines, including test ordering, result schemas, and escalation rules.

Core Features & Use Cases

Defines a mandatory integration test sequence (connectivity, data flow, throughput, backpressure, error handling) and a structured JSON result.
Provides guidance on simulation tooling, multi-clock domain considerations, and acceptance-criteria traceability for Tier 4 progress.
Use Case: teams adopt a consistent policy to ensure reproducible verification and clear escalation paths across cocotb, Verilator, and SV TB workflows.

Quick Start

Follow the Tier 4 integration test policy to structure your integration tests and results.

Frequently Asked Questions about rtl-p5s-integration-test-policy

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

FAQPage Schema

What is a Tier 4 integration testing policy for RTL designs?▼

RTL integration testing validates end-to-end hardware verification pipelines by standardizing test phase ordering, JSON result schemas, and escalation rules. It covers static connectivity, data flow, backpressure scenarios, and e2e reference checks to ensure reproducible verification across cocotb, Verilator, and SV TB workflows.

How do I structure integration tests for RTL designs using cocotb or Verilator?▼

Structure RTL integration tests by following a mandatory sequence: connectivity, data flow, throughput, backpressure, and error handling. Generate required simulation artifacts and output results using a structured JSON schema to ensure acceptance-criteria traceability across cocotb, Verilator, or SV TB workflows.

Does the Tier 4 integration test policy support SystemVerilog testbench workflows?▼

Yes, the Tier 4 integration test policy explicitly supports SV TB workflows alongside cocotb and Verilator. It provides guidance on multi-clock domain considerations and standardizes test phase ordering and result schemas across these simulation tools.

What is the required result format for RTL integration testing verification?▼

The required result format for RTL integration testing is a structured JSON schema. This schema standardizes test outcomes across connectivity, data flow, backpressure, and e2e reference checks, integrating with tier transitions and acceptance-criteria traceability guidance.

How do I handle backpressure scenarios in RTL integration testing?▼

Handle backpressure scenarios in RTL integration testing by following the mandatory test sequence defined by the Tier 4 policy. This includes testing backpressure alongside static connectivity and data flow, then documenting results in the structured JSON schema.

When do I need a standardized integration test policy for RTL verification pipelines?▼

You need a standardized integration test policy for RTL verification pipelines when adopting consistent practices across cocotb, Verilator, and SV TB workflows. It ensures reproducible verification, clear escalation paths, and acceptance-criteria traceability for multi-clock domain designs.