openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: dvazquezd

Verify code implementations against specifications, tasks, and design documents.

Updated Aug 23, 2026

Search Tags:#testing #code review #verification #compliance #change management #openspec

Ready to run

npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-verify-change-dvazquezd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/dvazquezd/openspec-governance/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-verify-change-dvazquezd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately reflect the defined change artifacts (specs, tasks, design) before archiving, preventing inconsistencies and ensuring quality.

Core Features & Use Cases

Automated Verification: Checks task completion, spec coverage, requirement implementation, scenario coverage, and design adherence.
Issue Reporting: Generates a detailed report categorizing issues as CRITICAL, WARNING, or SUGGESTION with actionable recommendations.
Use Case: After completing development for a new feature, use this Skill to confirm that all user stories are implemented, all design decisions are followed, and all tasks are marked as done before submitting for review.

Quick Start

Use the openspec verify change skill to check the status of the 'add-user-profile' change.

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 that code implementations align with change specifications?▼

To verify code implementations align with change specifications, you can run automated checks against your change artifacts. This process evaluates task completion, spec coverage, and requirement implementation to ensure development adheres to defined standards before archiving.

What is the best way to check task completion and design adherence before archiving changes?▼

The best way to check task completion and design adherence is by verifying change implementations against specs, tasks, and design documents. This generates a detailed report categorizing issues as CRITICAL, WARNING, or SUGGESTION with actionable recommendations.

Do I need the openspec CLI to verify change implementation against specs?▼

Yes, you need the openspec CLI installed. Verifying change implementation against specs requires the openspec CLI and access to change directories and associated artifacts to perform automated compliance and coverage checks.

How do I generate a report for unimplemented user stories and scenario coverage?▼

You can generate a report for scenario coverage and unimplemented user stories by verifying change implementation against specs. The resulting report categorizes issues by severity, including CRITICAL, WARNING, and SUGGESTION, to guide code review.

When should I run a compliance check on my software development workflows?▼

You should run a compliance check after completing development for a new feature and before submitting for review. This ensures all user stories are implemented, design decisions are followed, and tasks are marked done before archiving changes.