openspec-verify-change

Verify implementation alignment with change artifacts and produce a verification report.

6|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-verify-change-remiverdiesen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-verify-change-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confirm that an implementation actually matches the expected change artifacts before you archive or ship it, reducing missed requirements and late-stage rework.

Core Features & Use Cases

  • Completeness Checks: Reviews task checklists and flags anything still incomplete.
  • Spec Coverage: Compares requirements and scenarios from change specs against the codebase.
  • Correctness and Coherence: Checks implementation evidence, design alignment, and pattern consistency to surface gaps or mismatches.
  • Use Case: Use this Skill when a feature is supposedly finished and you need a clear verification report showing what is done, what is missing, and what should be reviewed before approval.

Quick Start

Ask the skill to verify a named change and summarize any incomplete tasks, missing requirements, and design inconsistencies.

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 the specification before release?

Spec verification checks implementation against change artifacts by parsing tasks, tracing requirements, and assessing design adherence to produce an actionable report showing what is done, missing, or needs review before release.

What is design adherence assessment in change validation?

Design adherence assessment reviews implementation evidence and pattern consistency against design notes to surface gaps or mismatches between the actual codebase and expected change specifications.

How do I check scenario coverage and task completeness for a finished feature?

Check scenario coverage by comparing requirements and scenarios from change specs against the codebase, review task checklists, and flag incomplete tasks to generate a clear pre-archive verification report.

Can I use this for pre-archive review of delta specifications?

Yes, change validation applies to pre-archive review by determining whether code, tasks, and delta specifications are aligned before you ship or archive a completed feature.

Why does requirement tracing matter for release readiness checks?

Requirement tracing links change spec requirements directly to codebase implementation evidence, ensuring no missed requirements cause late-stage rework before archiving or shipping.

What is the best way to summarize incomplete tasks and missing requirements?

Run a verification report that flags incomplete task checklists, missing scenario coverage, and design inconsistencies to summarize incomplete tasks and missing requirements in one actionable output.