rtl-p4-rapid-impl-policy

Enforce lint, CDC, smoke, and block sanity gates for P4 modules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a compact policy to enforce minimal validation gates during rapid P4-based RTL implementation so engineers can iterate quickly without sacrificing basic correctness and integration sanity.

Core Features & Use Cases

  • Defines four rapid-mode gates: lint, CDC, smoke functional, and block sanity integration at module and touched-integration scope.
  • Specifies minimum pass criteria and escalation guidance to prefer smallest-scope fixes and clear root-cause summaries on repeat failures.
  • Includes team and compliance state templates to integrate with an orchestrator that populates module entries at runtime, enabling CI and quick-loop development workflows.

Quick Start

Run the rapid implementation policy to validate lint, CDC, smoke, and block sanity gates for a target P4 module before proceeding with full pipeline execution.

Frequently Asked Questions about rtl-p4-rapid-impl-policy

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

FAQPage Schema
How do I enforce lint and CDC checks for rapid P4 RTL development?

To enforce lint and CDC checks for P4 RTL, apply a rapid implementation policy that validates minimal gates including lint PASS, CDC PASS, and smoke tests to ensure basic correctness during quick-loop iterations.

What validation gates are required for P4 module block sanity integration?

P4 module block sanity integration requires four rapid-mode gates: lint, CDC, functional smoke, and block sanity integration at module and touched-integration scope, each needing a PASS status.

Can I use this rapid RTL policy for continuous integration workflows?

Yes, this rapid RTL policy suits continuous integration workflows by providing team and compliance state templates that integrate with an orchestrator to populate module entries at runtime during quick-loop development.

How should I handle failures during RTL smoke and block sanity checks?

Handle RTL smoke and block sanity check failures by applying minimal-scope fixes and providing clear root-cause summaries on repeat failures, guided by the policy's escalation criteria.

What is the best way to iterate quickly on P4-based modules without sacrificing correctness?

The best way to iterate quickly on P4-based modules is applying a compact rapid implementation policy that enforces minimal validation gates like lint, CDC, and smoke checks at module and touched-integration scope.