bazinga-validator
Validates BAZINGA completion claims with independent verification. Spawned ONLY when PM sends BAZINGA. Acts as final quality gate - verifies test failures, coverage, evidence, and criteria independently. Returns ACCEPT or REJECT verdict.
Security Assessment
About bazinga-validator
The bazinga-validator skill is designed to serve as a final quality assurance gate in an orchestration workflow. It is triggered only when a Project Manager issues a BAZINGA completion signal, indicating that all success criteria are believed to be satisfied. At this point, the skill independently verifies these claims by retrieving the defined success criteria and associated evidence, ensuring that the completion signal is justified. Its primary purpose is to prevent premature or incorrect acceptance of work by enforcing strict validation standards and requiring objective proof of completion.
This skill performs several key functions, including querying a centralized workflow database for success criteria, analyzing the Project Manager’s claimed status, and validating supporting evidence. It applies conditional logic to determine whether test execution is required, and if so, it identifies the appropriate test command, executes tests with configurable timeouts, and parses results to detect failures. The validator enforces zero tolerance for failing tests when such criteria are present and ensures that all required conditions are met before issuing a verdict. The output is a structured ACCEPT or REJECT decision based on independent verification.
The bazinga-validator is particularly useful in automated development pipelines, orchestration systems, and collaborative engineering environments where multiple agents or roles contribute to task completion. It is intended for use by orchestrators and systems that require a reliable, unbiased validation step before finalizing workflows. By acting as a skeptical and evidence-driven gatekeeper, it helps maintain high quality standards and reduces the risk of incomplete or incorrect deliverables being accepted.
FAQ
When should the bazinga-validator skill be invoked?
It should only be invoked after the Project Manager sends a BAZINGA completion signal, indicating that all success criteria are believed to be met.
Does the skill always run tests during validation?
No, tests are only executed if test-related criteria are detected in the success criteria. If no such criteria exist, the test verification step is skipped.
What happens if tests fail during validation?
Any test failure results in a REJECT verdict, as the validator enforces zero tolerance for failing tests when they are part of the success criteria.
What tools does the bazinga-validator rely on?
It uses Bash, Read, Grep, and other skills such as bazinga-db-workflow to retrieve and verify success criteria and execute validation steps.
What if test execution times out?
If a timeout occurs, the validator checks for recent test evidence provided by the Project Manager. If no valid evidence is available, it returns a REJECT verdict due to inability to verify test status.
Install bazinga-validator
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mehdic/bazinga