verify-implementation

Final verification after implementation is complete. Use when all tasks are done to verify against spec, run full tests, update roadmap, and generate final report.

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 18, 2025

When & Why to Use This Skill

This Claude skill automates the final verification phase of the software development lifecycle. it ensures that completed implementations strictly adhere to technical specifications, pass all quality gates, and are properly documented. By integrating automated testing, code quality checks, and roadmap synchronization, it provides a robust framework for maintaining high engineering standards and project transparency.

Use Cases

  • Feature Completion Audit: Systematically verifying that a newly implemented feature meets all requirements and acceptance criteria defined in the project specification.
  • Automated Quality Assurance: Executing full test suites and static analysis tools (linters/type checkers) to ensure code reliability and prevent regressions before final delivery.
  • Project Documentation & Reporting: Automatically generating final verification reports and updating product roadmaps to keep stakeholders informed of development progress and milestone completion.
nameverify-implementation
descriptionFinal verification after implementation is complete. Use when all tasks are done to verify against spec, run full tests, update roadmap, and generate final report.

Verify Implementation

Complete final verification and documentation after implementation.

When to Use

  • All task groups in tasks.md are complete
  • Ready for final verification
  • Need to update roadmap and generate report

Workflow

  1. Verify Against Spec

    • Load amp-os-implementation-verifier skill
    • Check all requirements from spec.md are met
    • Verify acceptance criteria pass
  2. Run Full Test Suite

    • Execute complete test suite
    • Verify no regressions
    • Check test coverage if applicable
  3. Code Quality Check

    • Run linter and type checker
    • Load amp-os-standards-global to verify patterns
    • Address any issues
  4. Update Roadmap

    • Mark feature complete in amp-os/product/roadmap.md
    • Update milestone status
    • Note any scope changes
  5. Generate Final Report

  6. Oracle Review (Recommended)

    • Call oracle: "Review this implementation against the spec"
    • Address any concerns raised

Resources

Amp Tools to Use

  • oracle - Final review and validation
  • todo_write - Mark feature complete
  • Build/test commands from AGENTS.md

Verification Checklist

  • All spec requirements implemented
  • All acceptance criteria pass
  • Full test suite passes
  • No lint/type errors
  • Documentation updated
  • Roadmap updated
  • Final report generated