implementation-verifier
Verify implementation completeness against spec and tasks. Use after implementation to ensure all tasks are complete, tests pass, and code meets quality standards before marking feature done.
When & Why to Use This Skill
The Implementation Verifier is a robust Claude skill designed to automate the final validation phase of software development. It systematically cross-references completed code against original specifications and task lists to ensure 100% feature completeness, adherence to quality standards, and successful test execution, effectively acting as an automated quality gate before production release.
Use Cases
- Feature Completion Audit: Automatically verify that all items in a project's task list are marked as complete and correctly implemented before closing a ticket.
- Pre-Merge Quality Check: Use the skill to run test suites, linters, and type checkers to ensure new code meets the repository's quality benchmarks.
- Specification Alignment: Compare the final implementation against the initial design spec to identify any functional gaps or missing requirements.
- Automated Verification Reporting: Generate standardized markdown reports summarizing task status, test coverage, and build results for team reviews and documentation.
| name | implementation-verifier |
|---|---|
| description | Verify implementation completeness against spec and tasks. Use after implementation to ensure all tasks are complete, tests pass, and code meets quality standards before marking feature done. |
Implementation Verifier
Validate that implementation matches specification and all tasks are complete.
When to Use
- After completing all tasks in tasks.md
- Before marking a feature as done
- When reviewing implementation quality
Verification Process
Load Checklist
Gather Artifacts
- Read
amp-os/specs/[feature]/spec.md - Read
amp-os/specs/[feature]/tasks.md - Use
todo_readto check task completion status
- Read
Verify Each Category
- Task Completion
- Test Coverage
- Code Quality
- Spec Alignment
- Documentation
Run Verification Commands
- Execute test suite
- Run linter/type checker
- Verify build succeeds
Generate Report
- Save to
amp-os/specs/[feature]/verifications/final-verification.md
- Save to
Output Format
## Implementation Verification: [Feature Name]
### Task Completion: X/Y tasks complete
### Test Results
- Tests: X passed, Y failed
- Coverage: X%
### Code Quality
- Linting: ✅/❌
- Type Check: ✅/❌
- Build: ✅/❌
### Verdict: COMPLETE / INCOMPLETE
Amp Tools to Use
todo_read- Check task statusBash- Run tests, lint, buildfinder- Locate implementation files