openspec-verify-change

Verify code implementations against change artifacts, tasks, requirements, and design documents.

1|Updated Feb 7, 2026

Search Tags:#code quality #testing #devops #implementation #verification #change management

Ready to run

npx skills add https://github.com/nuitsjp/teams-board --skill openspec-verify-change-nuitsjp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/nuitsjp/teams-board/tree/main/.rulesync/skills/openspec-verify-change
Command: npx skills add https://github.com/nuitsjp/teams-board --skill openspec-verify-change-nuitsjp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your code implementation accurately reflects the defined change artifacts, preventing discrepancies and ensuring quality before archiving.

Core Features & Use Cases

Completeness Check: Verifies that all defined tasks are completed and requirements are covered.
Correctness Validation: Assesses if the implementation aligns with specified requirements and scenarios.
Coherence Review: Checks adherence to design decisions and code pattern consistency.
Use Case: Before merging a feature branch, use this Skill to automatically verify that all user stories and design specifications have been correctly implemented in the code.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the change named 'feature-x'.

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 matches design documents before merging?▼

To verify code implementation matches design documents, you can automatically check completeness, correctness, and coherence against spec files to ensure quality and consistency before archiving or deployment.

What is change artifact verification in software engineering?▼

Change artifact verification is the process of assessing whether code implementations precisely match specified tasks, requirements, and design documents to prevent discrepancies in development workflows.

How do I check if all requirements and user stories are covered in my code?▼

To check if all requirements and user stories are covered, perform a completeness check that analyzes your code against spec files to verify all defined tasks are completed and requirements are fully addressed.

Can I validate code pattern consistency and adherence to design decisions automatically?▼

Yes, you can validate code pattern consistency through a coherence review that automatically checks if your implementation adheres to specified design decisions across the codebase.

When do I need to validate implementation against change artifacts in a DevOps workflow?▼

You need to validate implementation against change artifacts before merging a feature branch or archiving code, ensuring that code implementations accurately reflect defined change specifications and preventing discrepancies.

Does code implementation verification work without external dependencies?▼

Yes, code implementation verification works without external dependencies, relying solely on its internal scripts and references to analyze code against spec files and design documents.