rtl-block-contract-test-policy

Automate contract testing and merge-time verification for block-parallel RTL development.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Block-parallel RTL development requires consistent contract testing across multiple blocks to prevent integration regressions. This Skill provides a structured framework for contract tests, merge-time verification, and stub generation to streamline safe, upstream-first merges.

Core Features & Use Cases

  • Interface contract tests ensure signals conform to interface definitions.
  • Timing contract checks verify handshake latency, throughput, and domain crossing rules.
  • Stub generation rules provide deterministic mocks for blocks during integration testing and progressively replaced by real blocks as upstream merges occur.
  • Merge-time verification procedures enforce test order, pass/fail criteria, and a retry policy for failed merges.
  • Stub replacement during merges ensures integration tests reflect real blocks as dependencies are satisfied.

Quick Start

Follow this policy to generate contract tests, validate interfaces and timing contracts, and orchestrate upstream-first merges with stub replacement.

Frequently Asked Questions about rtl-block-contract-test-policy

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

FAQPage Schema
How do I enforce contract testing for block-parallel RTL merges?

Block-parallel RTL contract testing enforces interface conformity, timing assertion checks, and automatic stub generation during upstream-first merges to prevent integration regressions. It applies structured merge-time verification procedures to ensure safe block integration.

How does automatic stub generation work for RTL integration testing?

Automatic stub generation provides deterministic mocks for RTL blocks during integration testing. These counterpart stubs are progressively replaced by real blocks as upstream merges occur, ensuring integration tests accurately reflect dependencies as they are satisfied.

What timing checks are required for RTL block contract tests?

RTL block contract tests require timing assertion checks to verify handshake latency, throughput, and domain crossing rules. These timing contract checks ensure signals conform to interface definitions and prevent integration failures during block-parallel development.

Can I define a retry policy for failed RTL block merges?

Failed RTL block merges use a defined retry policy implemented within merge-time verification procedures. The policy enforces specific test order, pass/fail criteria, and merge-order rules to orchestrate safe upstream-first merges with automatic stub replacement.

What is the merge-order rule for upstream-first RTL development?

The upstream-first merge-order rule requires integrating upstream blocks before downstream dependencies. Merge-time verification enforces this sequence, progressively replacing counterpart stubs with real blocks as dependencies are satisfied during the block-parallel RTL pipeline.