openspec-verify-change

Verify code implementation against OpenSpec change artifacts and task completion.

139|27|Updated Nov 9, 2014

Search Tags:#requirements traceability #design consistency #test coverage #task tracking #change management #openspec #spec verification

Ready to run

npx skills add https://github.com/nfe/client-nodejs --skill openspec-verify-change-nfe

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete, incorrect, or diverging implementations from being archived by systematically checking task completion, spec requirement coverage, scenario coverage, and design consistency against the selected OpenSpec change artifacts.

Core Features & Use Cases

Change-focused verification: Validates an implementation against the selected change’s specs and tasks, ensuring nothing essential is missing before you close the work.
Completeness checks: Detects incomplete tasks from tasks.md and flags missing requirement implementations based on delta spec requirements.
Correctness & coherence checks: Looks for evidence of requirement/scenario coverage and highlights divergences from design decisions to improve confidence in alignment.

Quick Start

Ask the system to run openspec-verify-change for the specific change you want to verify, and then follow the on-screen prompts to select the change if you did not provide its name.

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 spec alignment before archiving a change?▼

Spec verification for change management systematically checks task completion, requirement coverage, and scenario coverage against OpenSpec change artifacts. It prevents incomplete or incorrect implementations from being archived by validating code matches delta specs and tasks.md.

How does requirements traceability work for spec-driven development?▼

Requirements traceability maps delta spec requirements and scenarios directly to implementation evidence. It validates design consistency and flags divergences from design decisions, ensuring your code changes align with the specified OpenSpec artifacts before archiving.

What is the best way to check test coverage for OpenSpec changes?▼

Check test coverage for OpenSpec changes by mapping scenarios from delta specs to implementation evidence. The verification process looks for proof of scenario coverage and highlights missing requirement implementations or divergences from design decisions.

Can I use openspec-verify-change with a custom status schema?▼

Yes, openspec-verify-change supports schema-aware artifact loading via openspec status and instructions apply. It works with optional design.md and status schema metadata located alongside tasks.md and delta specs under openspec/changes/<name>/.

Why does my implementation verification report show missing requirement coverage?▼

Your verification report flags missing requirement coverage because the system detects incomplete tasks from tasks.md and maps delta spec requirements to implementation evidence. It generates a prioritized completeness and correctness report highlighting these gaps.