openspec-verify-change

Validate software changes against openspec artifacts for completeness and correctness.

Updated Aug 27, 2026

Search Tags:#verification #tasks #code #openspec #specs #change

Ready to run

npx skills add https://github.com/brianzzs/GreenFiveInnings --skill openspec-verify-change-brianzzs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to confirm that a code change fully satisfies its associated specifications, tasks, and design decisions before archiving, leading to incomplete or inconsistent releases.

Core Features & Use Cases

Artifact Retrieval: Lists available changes and pulls all related artifacts using the openspec CLI.
Multi-Dimensional Verification: Assesses completeness, correctness, and coherence of the implementation against tasks, specs, and design documents.
Structured Reporting: Generates a detailed verification report with severity‑ranked issues and actionable recommendations.
Use Case: A developer finishes a feature branch and wants to ensure every requirement, scenario, and design decision is addressed before merging and archiving the change.

Quick Start

Ask the skill to verify the implementation of change “FeatureX” before archiving.

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 changes match specifications before archiving?▼

You can verify a feature implementation against specs by retrieving all related change artifacts via the openspec CLI and assessing completeness, correctness, and coherence. This multi-dimensional verification produces a structured report with severity-ranked issues and actionable recommendations before merging.

What is change artifact verification in software engineering?▼

Change artifact verification validates that a software change aligns with its associated specifications, tasks, and design decisions. It assesses implementation completeness, correctness, and coherence to prevent incomplete or inconsistent releases before archiving.

Do I need the openspec CLI to validate implementation completeness?▼

Yes, the openspec CLI is required to validate implementation completeness. The verification process requires the openspec CLI to list available changes, retrieve status, and process artifacts for multi-dimensional verification against tasks and design documents.

How do I generate a verification report for a feature branch before merging?▼

Generate a verification report by listing available changes and retrieving related artifacts using the openspec CLI. The process assesses the feature branch implementation against specs and tasks, outputting a detailed report with severity-ranked issues and actionable recommendations.

Why does my code change verification fail before archiving?▼

Code change verification fails before archiving when the implementation does not fully satisfy its associated specifications, tasks, or design decisions. The structured verification report identifies gaps in completeness, correctness, and coherence by listing severity-ranked issues.