verify

Compare source code against baseline specifications to detect deviations.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/augentic/specify --skill verify-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/augentic/specify/tree/main/plugins/spec/skills/verify
Command: npx skills add https://github.com/augentic/specify --skill verify-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure your codebase remains aligned with its documented specifications, preventing unexpected behavior and maintaining integrity.

Core Features & Use Cases

  • Drift Detection: Compares current code against baseline specifications to identify discrepancies.
  • Capability Verification: Can verify specific functionalities or the entire codebase against specs.
  • Use Case: After a series of code changes, use this Skill to confirm that all implemented features still precisely match the requirements outlined in your spec.md files.

Quick Start

Run the verify skill to check the codebase against all baseline specifications.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I detect code drift from baseline specifications?

To detect code drift, compare current source code against baseline specifications to identify discrepancies, missing behaviors, and unspecified logic using semantic matching against requirement scenarios.

What is specification compliance in software development?

Specification compliance ensures your codebase remains aligned with documented architectural blueprints and predefined requirements, preventing unexpected behavior and maintaining codebase integrity over time.

Can I verify specific functionalities instead of the entire codebase?

Yes, capability verification supports checking specific functionalities or the entire codebase against baseline specs, identifying covered, drifted, missing, and unspecified behaviors based on semantic matching.

When do I need to run code verification against requirements?

You need code verification after a series of code changes to confirm that all implemented features still precisely match the requirements outlined in your spec.md files and architectural blueprints.

What's the best way to find undocumented behaviors in source code?

The best way to find undocumented behaviors is comparing current source code against baseline specifications, which identifies unspecified behaviors by checking code logic against documented requirement scenarios.

What are the limitations of automated drift detection?

Drift detection relies on semantic matching of code logic against requirement scenarios, requiring comprehensive spec.md baseline files to effectively identify covered, drifted, missing, and unspecified behaviors.