When does the Implementation Verifier skill activate?

It is triggered automatically after the implementation phase is complete and before a task is marked as finished, specifically when critical components are involved.

Does it check for specific programming libraries?

Yes, it includes built-in verification for essential packages such as netmiko, neo4j, ollama, and fastapi to ensure the environment is correctly configured.

How does it compare code against requirements?

It parses the PRD and tasks.json to extract critical requirements, then scans the generated code to verify imports, boundaries, and logic without substitutions.

What happens if the verification fails?

The skill generates a compliance report listing missing components and substitution warnings, signaling a VERIFICATION_FAILED state to block progression until fixes are applied.

Implementation Verifier

Name: Implementation Verifier
Author: turbobeest

byturbobeest

•

Security & Testing

Validates implemented code against PRD requirements to ensure architectural integrity and zero-omission compliance.

About

The Implementation Verifier skill provides a rigorous validation layer for Claude Code, ensuring that every requirement specified in your Product Requirements Document (PRD) is accurately reflected in the final codebase. By automatically scanning generated files, verifying mandatory package imports, and auditing architectural boundaries, it prevents unauthorized substitutions and accidental shortcuts. This skill is essential for developers who need to guarantee that AI-generated implementations strictly adhere to technical specifications and security standards before deployment.

Key Features

Automated requirement matching against PRD documentation
Architectural boundary auditing to maintain separation of concerns
Deep-scan package verification for libraries like FastAPI, Neo4j, and Netmiko
Detection of unauthorized code substitutions or omitted features
Comprehensive compliance reporting with actionable fix recommendations
2 GitHub stars

Use Cases

Ensuring a newly developed API includes all security middlewares specified in the design phase
Auditing complex system migrations to confirm no critical dependencies or logic gates were skipped
Automating the pre-completion verification step to maintain high-fidelity code quality

About

Key Features

Automated requirement matching against PRD documentation
Architectural boundary auditing to maintain separation of concerns
Deep-scan package verification for libraries like FastAPI, Neo4j, and Netmiko
Detection of unauthorized code substitutions or omitted features
Comprehensive compliance reporting with actionable fix recommendations
2 GitHub stars

Use Cases

Ensuring a newly developed API includes all security middlewares specified in the design phase
Auditing complex system migrations to confirm no critical dependencies or logic gates were skipped
Automating the pre-completion verification step to maintain high-fidelity code quality