rtl-p5a-functional-closure-policy

Enforce P5A functional closure gates for RTL design regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent, project-level enforcement of P5A functional closure criteria so that regressions, coverage shortfalls, and incomplete requirement traceability do not advance to later phases or silicon.

Core Features & Use Cases

  • Hierarchical Closure Rules: Defines module, block, and top-level checks and an exit gate that blocks progression on functional FAILs.
  • Acceptance Criteria Enforcement: Specifies AC-level handling for Critical/High ac_ids including WARNING, FAIL, VERIFIED, and FORMAL gating behavior.
  • Coverage & Traceability Targets: Documents required multi-seed regression, per-target coverage goals, and a requirement traceability matrix check.
  • Use Case: Run this policy during P5A internal verification to evaluate multi-seed regression stability, coverage attainment, and AC status before permitting P5B/P6 entry.

Quick Start

Run the P5A functional closure policy to evaluate module, block, and top regression, coverage, and traceability status and report any blocking ACs or coverage gaps.

Frequently Asked Questions about rtl-p5a-functional-closure-policy

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

FAQPage Schema
What is functional closure in RTL verification and how does it gate phase progression?

The P5A functional closure policy blocks phase progression by requiring multi-seed regression stability, coverage target attainment, and VERIFIED or FORMAL status for Critical and High acceptance criteria.

How do I enforce acceptance criteria verification for Critical and High requirements at the P5A exit gate?

Enforce acceptance criteria at the P5A exit gate by requiring VERIFIED or FORMAL statuses for Critical and High ac_ids, blocking any functional FAILs or unresolved WARNINGs from P5B or P6 progression.

Does P5A functional closure require multi-seed regressions and coverage targets at module, block, and top levels?

Yes, P5A functional closure requires multi-seed regressions and defined per-target coverage goals across module, block, and top-level verification checkpoints before evaluating the exit gate.

How do I check requirement traceability status before permitting P5B and P6 entry?

Check requirement traceability by running the functional closure policy to evaluate the traceability matrix, ensuring all Critical and High acceptance criteria reach VERIFIED or FORMAL statuses before P5B entry.

What happens if there are coverage shortfalls or incomplete requirement traceability during internal RTL regressions?

Coverage shortfalls or incomplete requirement traceability during internal regressions block progression to later phases, preventing unstable RTL designs from advancing to the P5A exit gate or silicon.

When should I run the P5A functional closure policy during the RTL verification flow?

Run the P5A functional closure policy during internal module, block, and top-level verification checkpoints to evaluate regression stability, coverage, and traceability before permitting P5B or P6 entry.