rat-p4p5-impl-verify-policy

Enforce Phase 4 to 5 gate criteria before RTL verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy-focused guide codifies prerequisite checks, phase-gate criteria, and feedback-loop classifications to ensure Phase 4→5 transitions occur only when upstream artifacts meet required quality standards.

Core Features & Use Cases

  • Defines artifact gates and quality gates for RTL-to-Verification handoffs.
  • Specifies prerequisite artifacts, state tracking, and escalation pathways to maintain traceability across Phases 1-5.
  • Provides checklists and templates to audit Phase 4 readiness and ensure compliance with the overall design pipeline.

Quick Start

Review Phase 4→5 gates and verify artifacts and quality gates before proceeding to RTL verification.

Frequently Asked Questions about rat-p4p5-impl-verify-policy

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

FAQPage Schema
What is a phase gate policy for RTL verification handoff?

You can enforce phase gate discipline by applying prerequisite artifact checks and predefined quality criteria. This policy specifies gate criteria, state management tracking, and structured review artifacts to ensure compliance before verification begins.

How do I audit Phase 4 readiness before proceeding to RTL verification?

You audit Phase 4 readiness by using checklists and templates to verify prerequisite artifacts and state tracking. This ensures upstream quality standards are met and maintains traceability across the design pipeline before the handoff.

Do I need specific upstream artifacts to pass the architecture-to-verify phase gate?

Yes, specific prerequisite artifacts are required to pass the phase gate. The policy codifies artifact existence checks and state tracking across Phases 1-5 to guarantee that upstream design outputs satisfy required quality standards.

What happens if artifacts fail the quality gate criteria during the phase transition?

When artifacts fail quality gate criteria, the policy classifies feedback loops and specifies escalation pathways. This structured feedback handling ensures traceability and prevents the Phase 4 to Phase 5 transition until standards are met.

Can I use this phase gate policy to maintain traceability across the entire design pipeline?

Yes, you can use this policy to maintain traceability across the design pipeline. It specifies state tracking, prerequisite artifacts, and escalation pathways spanning Phases 1-5 to ensure continuous compliance during the architecture-to-verify workflow.