skills.rest
babyworm
babywormCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rtl-p4s-bugfix-policy

Enforce a four-step RTL bug-fix sequence with linting, testbench updates, and verification markers.

43|9|Updated Feb 25, 2026
Search Tags:#workflow#verification#lint#escalation#bugfix#rtl#testbench
One-click install
npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-p4s-bugfix-policy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rtl-p4s-bugfix-policy
Source: https://github.com/babyworm/rtl-agent-team/tree/main/skills/rtl-p4s-bugfix-policy
Command: npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-p4s-bugfix-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy codifies a mandatory, auditable workflow for diagnosing and fixing RTL bugs so teams avoid ad-hoc fixes, missed verification, and inconsistent escalation during the RTL verification phase.

Core Features & Use Cases

  • Mandatory 4-step sequence: Enforce analyze → fix+lint → testbench → functional verification per modified module to ensure disciplined progress and traceability.
  • Parallel UNIT_FIX decision tree: Define when fixes can run in parallel versus when sequential or integration-first handling is required, with rules for verification-done markers.
  • Escalation and checklists: Provide concrete escalation triggers, stop conditions, naming conventions, and a final checklist to satisfy project quality gates and handoffs.
  • Use Case: A verification engineer receives a failing test; use the policy to determine required linting rounds, testbench updates, whether to run parallel module fixes, and when to escalate to architects.

Quick Start

Apply the RTL Bug Fix Policy to the failing module by following the mandated analyze, fix and lint, testbench update, and functional verification sequence and record escalation or lesson-learned outcomes.

Frequently Asked Questions about rtl-p4s-bugfix-policy

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

FAQPage Schema
What is a mandatory RTL bug-fix workflow for module-level verification?▼

A mandated RTL bug-fix sequence enforces analyze, fix, lint, testbench update, and functional verification per modified module to prevent ad-hoc fixes and ensure traceability during unit and integration verification.

How do I sequence linting and testbench updates when fixing RTL bugs?▼

Sequence RTL bug fixes by analyzing the issue, applying the fix with required lint rounds, updating the per-module testbench, and completing functional simulation to create verification-done markers.

When should I run parallel module fixes during RTL verification?▼

Run parallel module fixes during RTL verification when the UNIT_FIX decision tree permits, otherwise sequential or integration-first handling is required to safely close the bug and record verification-done markers.

What triggers escalation during the RTL bugfix process?▼

Escalation triggers during the RTL bugfix process are concrete stop conditions defined by the policy, such as failing testbench updates or unresolved lint rounds, requiring handoff to architects.

Does this RTL bugfix policy apply to both unit and integration verification scenarios?▼

Yes, the RTL bugfix policy applies to unit and integration verification scenarios where linting, testbench updates, and functional simulation are required to close a bug and record verification-done markers.

Related Skills

Explore More Software Engineering Skills→
babywormbabyworm
43

rtl-document

Generate module-level Markdown documentation from SystemVerilog RTL sources and synthesis reports.

Community
Intermediate
vonomarapvonomarap

coordinator-blueprint-gates

Validates Architect outputs against governance gates and emits a BlueprintIssueReport on failure.

Community
Advanced
babywormbabyworm
43

rtl-p4s-bugfix

Enforce analyze, fix, lint, testbench, and simulation verification for modified SystemVerilog files.

Community
Advanced
burgebjburgebj

octopus-quick

Execute small software changes with atomic commits and state tracking.

Community
Intermediate