openspec-verify-change

Verify implementation completeness against openspec delta spec artifacts.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-verify-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/memorysaver/agentpit-gg/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-verify-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill verifies that an implementation matches the change artifacts (specs, tasks, and design) to ensure completeness, correctness, and coherence before archiving.

Core Features & Use Cases

  • Completeness checks: Validate that tasks and delta specs are fully addressed, with explicit recommendations for missing items.
  • Correctness checks: Assess whether implemented code aligns with change requirements, and flag potential divergences for review.
  • Coherence checks: Ensure design decisions and project patterns are followed, or clearly documented deviations.

Quick Start

  • Provide a change name when prompted, or let the skill request a selection from available changes with the openspec CLI.
  • Run the verification workflow: openspec status --change "<name>" --json, then openspec instructions apply --change "<name>" --json to load artifacts, and review the generated report.

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 my code changes match the specification before archiving?

Verification checks that your implementation matches change artifacts—specs, tasks, and design—for completeness, correctness, and coherence. Run `openspec status --change "<name>" --json` followed by `openspec instructions apply --change "<name>" --json` to load artifacts and generate a verification report.

What does a completeness check validate in a code review?

Completeness checks confirm that all tasks and delta specs in your change are fully addressed, with explicit recommendations flagging any missing items so nothing is overlooked before archiving.

Can I validate that my implementation follows project design patterns?

Yes. Coherence checks ensure design decisions and project patterns are followed, or clearly document deviations so reviewers understand intentional divergences from established conventions.

What do I need to run this verification on my changes?

You need the openspec CLI installed and access to delta spec artifacts stored under `openspec/changes/<change>/`, including spec files, tasks, and context data for your software project.

How does correctness validation flag misaligned code?

Correctness checks assess whether implemented code aligns with change requirements and surface potential divergences for review, helping catch gaps between specification and actual implementation.