rtl-block-interface-policy

What problem does it solve?

Prevents interface drift, integration breakage, and timing mismatches when multiple RTL blocks are developed in parallel by defining clear, enforceable interface rules and a verification workflow for Phase 2–4 block-parallel projects.

Core Features & Use Cases

• Defines file naming conventions and a shared package location for cross-block interface definitions.
• Specifies a required timing contract format to be embedded in each interface and locks timing during microarchitecture work.
• Declares which interface artifacts are frozen at Phase 2 exit and provides a hash-based verification command to detect freeze violations at merge time.
• Establishes valid/ready handshake, backpressure, and multi-beat transfer rules plus a multi-step freeze-violation escalation protocol involving worker, coordinator, and leader roles.
• Use case: a block worker detects a needed interface change during Phase 4, automatically verifies the freeze, and follows the escalation protocol to request a coordinated change.

Quick Start

Use the rtl-block-interface-policy skill to verify the Phase 2 interface freeze and report any freeze violations to the coordinator.