Agent skill
implementation-verifier-turbobeest-cursor-dev-system-2
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/implementation-verifier-turbobeest-cursor-dev-system-2
SKILL.md
Implementation Verifier Skill
Metadata
- skill_name: implementation-verifier
- activation_code: IMPLEMENTATION_VERIFIER_V1
- version: 1.0.0
- category: validation
- phase: post-implementation
Description
Verifies that implementation matches PRD requirements without substitutions or omissions.
Activation Criteria
- Triggered after Phase 3 (Implementation) completes
- Before marking any task as complete
- When critical components are involved
Workflow
- Extract critical requirements from PRD
- Check for required imports/packages
- Verify architectural boundaries
- Validate no unauthorized substitutions
- Generate compliance report
Validation Checks
Package Verification
required_packages = {
"netmiko": ["from netmiko import", "ConnectHandler"],
"neo4j": ["from neo4j import", "AsyncGraphDatabase"],
"ollama": ["ollama", "llama"],
"fastapi": ["from fastapi import", "FastAPI"]
}
Architecture Verification
- Check separation of concerns
- Verify security boundaries
- Ensure no shortcuts taken
Output
- Compliance report
- List of missing components
- Substitution warnings
- Recommendations for fixes
Integration Points
- Reads: PRD, tasks.json, generated code
- Writes: verification-report.json
- Signals: VERIFICATION_FAILED, VERIFICATION_PASSED
Example Activation
When implementation completes, this skill automatically:
- Scans all generated files
- Matches against PRD requirements
- Alerts on missing critical components
- Blocks progression until resolved
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?