openspec-verify-change

Validate code implementations against openspec CLI change artifacts.

1|Updated Feb 13, 2026

Search Tags:#quality assurance #code review #verification #compliance #change management #openspec

Ready to run

npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-verify-change-em-jones

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-verify-change-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately reflect the defined change specifications, design documents, and tasks, preventing inconsistencies and ensuring quality before archiving.

Core Features & Use Cases

Completeness Check: Verifies all tasks are done and requirements are addressed.
Correctness Validation: Assesses if implementation matches spec intent and covers scenarios.
Coherence Review: Checks adherence to design decisions and code patterns.
Use Case: Before merging a new feature, use this Skill to confirm that all user stories are implemented, the code follows the approved architecture, and all necessary tests are in place.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the change named 'user-authentication-flow'.

Frequently Asked Questions about openspec-verify-change

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

FAQPage Schema

How do I verify code implementation against change specifications before merging?▼

To verify code implementation against change specifications, use a validation process that checks task completeness, correctness against spec intent, and coherence with design documents. This pre-archival quality assurance ensures the code accurately reflects defined requirements and approved architecture.

What is change verification in software engineering quality assurance?▼

Change verification in quality assurance is the process of validating code implementation against change artifacts like specifications, tasks, and design documents. It ensures completeness, correctness, and coherence within a project before archiving or merging new features.

Do I need openspec-cli to validate implementation against specs?▼

Yes, you need openspec-cli to validate implementation against specs. The validation process scopes to changes within a project managed by the openspec CLI, relying on its infrastructure to access change artifacts and verify adherence to development standards.

How do I check if all user stories and tasks are implemented before archiving?▼

To check if all user stories and tasks are implemented, perform a completeness check and correctness validation against the change specifications. This confirms all requirements are addressed, the code matches spec intent, and necessary tests are in place.

What's the best way to ensure code follows approved architecture during change management?▼

The best way to ensure code follows approved architecture is to perform a coherence review during change verification. This checks adherence to design decisions and code patterns, confirming the implementation matches the approved architecture and design documents.

Why does my code implementation not match the defined change specifications?▼

Implementation may not match change specifications due to incomplete tasks, unaddressed requirements, or deviations from design decisions. Running a verification check identifies these gaps in completeness, correctness, and coherence before archiving.