specsafe-verify

Validate implemented code against specifications and test suites in SpecSafe.

3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill specsafe-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specsafe-verify
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.claude/skills/specsafe-verify
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill specsafe-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the crucial step of verifying that implemented code meets the defined specification and passes all tests, ensuring quality before moving to the next stage.

Core Features & Use Cases

  • Automated Test Execution: Runs the full test suite with coverage analysis.
  • Requirement Validation: Cross-references implementation against spec requirements and acceptance criteria.
  • Use Case: After a developer finishes implementing a new feature, this Skill can be invoked to automatically run all associated tests, check code coverage, and validate that all P0 requirements are met, providing a clear GO/NO-GO recommendation for QA.

Quick Start

Run the specsafe verify skill for the user authentication spec ID.

Frequently Asked Questions about specsafe-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate implemented code against spec requirements and test suites?

Code validation against spec requirements executes the full test suite, analyzes coverage, and cross-references implementation against acceptance criteria to ensure P0 requirements are met.

What happens when test coverage is insufficient during code validation?

When test coverage is insufficient during code validation, the process loops back to the development stage instead of advancing, ensuring all P0 criteria and coverage thresholds are met.

How does automated test execution check code quality and requirement adherence?

Automated test execution checks code quality by running the full test suite with coverage analysis, then cross-referencing the implementation against defined spec requirements for a GO/NO-GO recommendation.

Can I use this validation to transition code from the development stage to QA?

Yes, validation transitions code from the CODE stage to the QA stage upon successful validation, confirming that all tests pass and coverage meets the defined spec requirements.

What is the best way to automate requirement validation and coverage analysis after feature implementation?

Automating requirement validation after feature implementation involves running the full test suite, checking code coverage, and validating P0 requirements to provide a clear GO/NO-GO recommendation for QA.

Why does code validation loop back to development instead of moving to QA?

Code validation loops back to development when tests fail or coverage is insufficient, preventing the transition to QA until the implementation fully adheres to defined spec requirements.