openspec-verify-change

Verify code implementation against OpenSpec change artifacts and design documents.

30|1|Updated Feb 18, 2026

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

Ready to run

npx skills add https://github.com/pacaplan/flokay --skill openspec-verify-change-pacaplan

💬 Prompt for ChatGPT / Claude Chat▼

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

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 (specs, tasks, design), preventing drift and ensuring quality before archiving.

Core Features & Use Cases

Automated Verification: Checks for completeness, correctness, and coherence between code and specifications.
Issue Identification: Flags incomplete tasks, unimplemented requirements, design divergences, and pattern inconsistencies.
Use Case: After implementing a new feature based on design.md and tasks.md, use this Skill to automatically verify that all requirements are met and the implementation aligns with the design before merging the changes.

Quick Start

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

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 and design documents?▼

To verify code against change artifacts like specs and design documents, use an automated verification skill to check completeness, correctness, and coherence. It flags incomplete tasks, unimplemented requirements, and design divergences before merging changes.

What is the best way to prevent code drift from predefined specifications before archiving?▼

Preventing code drift requires automated verification of code implementation against change artifacts including specs, tasks, and design documents. This process ensures adherence to predefined specifications and flags pattern inconsistencies before archiving.

Do I need the OpenSpec CLI to check for unimplemented requirements in my software development workflow?▼

Yes, checking for unimplemented requirements requires the OpenSpec CLI to fetch and parse change-related files and code. This prerequisite allows the verification process to accurately identify incomplete tasks and design divergences.

How do I automatically flag incomplete tasks and design divergences after implementing a new feature?▼

You can automatically flag incomplete tasks and design divergences after implementing a new feature by running a verification check against your design.md and tasks.md files. This ensures all requirements are met and the implementation aligns with the design.

Does automated code verification work with tasks.md and design.md files?▼

Yes, automated code verification works with tasks.md and design.md files to ensure completeness and correctness. It applies to software development workflows requiring adherence to predefined specifications and design principles before merging changes.