From rtl-agent-team
Executes Tier 4 integration tests on RTL systems, verifying cross-module data flow, reset propagation, clock connectivity, handshake protocols, and end-to-end scenarios after unit and module tests pass.
npx claudepluginhub babyworm/rtl-agent-team --plugin rtl-agent-teamThis skill uses the workspace's default tool permissions.
<Purpose>
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Testing Tier Context:
Tier 1: Smoke Test — connectivity, R/W, basic ops (rtl-p4-implement Wave 4)
Tier 2: Unit Test — reference comparison, uarch features (rtl-p4s-unit-test)
Tier 3: Module Regr. — cocotb multi-seed (rtl-p5s-func-verify)
Tier 4: Integration — cross-module, end-to-end (THIS SKILL) ←
Outputs: sim/top/integration_results.json + sim/top/ test files.
<Use_When>
<Do_Not_Use_When>
<Execution_Policy>
skills/rtl-p5s-integration-test/templates/integration-tb-template.sv as scaffold
</Execution_Policy><Why_This_Exists> Modules that pass individually may fail when connected due to interface mismatches, protocol violations, or timing assumptions that don't hold across boundaries. Integration testing catches: width mismatches at module boundaries, reset not propagating to all sub-modules, backpressure not flowing through the pipeline, and data corruption at interface handoff points. These bugs are invisible to per-module testing. </Why_This_Exists>
The orchestrator runs static connectivity checks first, then dynamic data flow and handshake tests, and performs end-to-end reference comparison.All coding conventions, test ordering, result schema, and escalation rules are defined in the rtl-p5s-integration-test-policy skill (loaded via the orchestrator's skills: field).
Task(subagent_type="rtl-agent-team:p5s-integration-orchestrator", prompt="Execute Tier 4 integration testing. User input: $ARGUMENTS")
Do not perform any work directly. The orchestrator agent manages connectivity checks, data flow tests, and reference comparison.
reviews/phase-5-verify/integration-test-report.md — cross-module data flow, reset propagation, and clock connectivity resultssim/top/integration_results.json — per-test PASS/FAIL with failure details