verify

Verify implementation completeness against OpenSpec change artifacts using osf-verify.

Updated Aug 27, 2026

Search Tags:#validation #implementation #subagent #verify #openspec #code-review

Ready to run

npx skills add https://github.com/CuongTran69/tramthientra --skill verify-cuongtran69

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/verify
Command: npx skills add https://github.com/CuongTran69/tramthientra --skill verify-cuongtran69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps validate that an implementation matches the intended change artifacts before archiving, ensuring completeness, correctness, and coherence across specifications and delivered code.

Core Features & Use Cases

Context-aware verification: Use an OpenSpec change name or an implementation summary to gather relevant artifacts automatically.
Pre-archive validation: Check that implemented behavior matches expected outcomes and detect omissions or inconsistencies.
Use Case: After finishing an implementation, run verification to ensure the code, tests, and docs align with the change spec before closing the change.

Quick Start

Ask the verify skill to validate that the recent implementation matches the change artifacts and launch the verification subagent with subagent_type: osf-verify.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I validate my code implementation against change specifications before archiving?▼

To validate implementation against change specifications, you can use a verification subagent to automatically check code, tests, and docs for completeness and alignment with the OpenSpec change artifacts before archiving.

What is the best way to ensure code matches an OpenSpec change artifact?▼

Ensuring code matches an OpenSpec change artifact involves running context-aware verification that automatically gathers relevant artifacts and checks implemented behavior against expected outcomes to detect omissions or inconsistencies.

Can I verify an implementation summary without manually providing all change artifacts?▼

Yes, you can verify an implementation summary without manual artifact collection by providing just the OpenSpec change name or summary, which allows the verification subagent to automatically gather and validate the relevant artifacts.

How do I check for omissions or inconsistencies after finishing a code implementation?▼

Checking for omissions or inconsistencies after finishing an implementation requires running a pre-archive validation process that compares delivered code and configurations against the change spec to ensure expected outcomes are met.

Does code review verification work with OpenSpec changes and configuration updates?▼

Code review verification works with OpenSpec changes and configuration updates by launching an osf-verify subagent to perform artifact checks and consistency validations across the delivered code and specifications.