skills.rest
zhentingWu-wzt
zhentingWu-wztCOMMUNITY
Explore all skills by this author →
GitHub

openspec-verify-change

Audit code implementation against openspec change artifacts and generate verification reports.

6|Updated May 25, 2026
Search Tags:#spec-driven#verification#compliance#quality-assurance#openspec#code-review
One-click install
npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill openspec-verify-change-zhentingwu-wzt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/openspec-verify-change
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill openspec-verify-change-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the gap between technical specifications and actual code implementation by ensuring that all tasks, requirements, and design decisions are correctly reflected in the codebase before archiving.

Core Features & Use Cases

  • Completeness Verification: Automatically audits task lists and requirement coverage to ensure no work is left unfinished.
  • Correctness & Coherence Checks: Validates that the implementation aligns with defined scenarios and architectural design patterns.
  • Use Case: Before finalizing a feature branch, use this skill to generate a comprehensive report that identifies missing requirements, incomplete tasks, or deviations from the original design document.

Quick Start

Run the openspec-verify-change skill to audit the current implementation against the active change artifacts.

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 technical specifications before merging?▼

Spec-driven verification audits task completeness, requirement correctness, and architectural coherence by parsing JSON status outputs and artifact files to generate actionable verification reports.

What is the best way to check if a feature branch meets all design document requirements?▼

Completeness verification automatically audits task lists and requirement coverage to ensure no work is left unfinished, generating a comprehensive report before finalizing the branch.

How do I audit code completeness and requirement correctness using openspec?▼

Operating within the openspec CLI environment, the verification process parses JSON status outputs and artifact files to audit code completeness and requirement correctness.

Do I need JSON status outputs and artifact files to perform spec-driven compliance checks?▼

Yes, spec-driven compliance checks require parsing JSON status outputs and artifact files including specifications, tasks, and design documents to generate actionable verification reports.

When should I run a verification check against change artifacts?▼

You should run a verification check against change artifacts before finalizing a feature branch to ensure the codebase correctly reflects all tasks, requirements, and design decisions before archiving.

Related Skills

Explore More Software Engineering Skills→
pabloimrik17pabloimrik17

openspec-ff-change

Automate creation of OpenSpec change artifacts within CLI workflows.

Community
Intermediate
jimmymalhanjimmymalhan
1

conflict-resolution

Resolve Git merge conflicts by stashing changes, pulling main, and verifying codebase integrity.

Community
Advanced
mrclrchtrmrclrchtr
54

openspec-ff-change

Generate OpenSpec change artifacts in dependency order using the openspec CLI.

Community
Advanced
em-jonesem-jones
1

openspec-verify-change

Validate code implementations against openspec CLI change artifacts.

Community
Advanced