openspec-verify-change

Validate implemented code against delta specifications and generate a structured verification report.

6|Updated Feb 13, 2021
One-click install
npx skills add https://github.com/dezkareid/dezkareid --skill openspec-verify-change-dezkareid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/dezkareid/dezkareid/tree/main/design-system/design-tokens/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/dezkareid/dezkareid --skill openspec-verify-change-dezkareid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify that a change implementation matches the associated artifacts (specs, tasks, and design decisions) before archiving.

Core Features & Use Cases

  • Delta spec coverage validation
  • Task completion mapping to requirements
  • Correctness and coherence checks against design decisions
  • Structured verification report with prioritized issues

Quick Start

Provide the change name and trigger the verification to generate a report you can review 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 a change implementation against its delta specs?

To verify a change implementation against delta specs, trigger the verification process with the change name to validate code alignment with requirements, scenarios, and design decisions. The process generates a structured verification report highlighting CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations for review before archiving.

What is delta spec coverage validation for software changes?

Delta spec coverage validation is a structured verification process that checks whether implemented code aligns with associated delta specifications and tasks. It assesses completeness, correctness, and coherence across requirements and design decisions, producing a formal report with prioritized issues to ensure implementation matches artifacts before archiving.

How do I check task completion mapping to requirements before archiving?

You can check task completion mapping by running a verification process that validates implemented code against delta specifications and design decisions. The verification assesses completeness and coherence, generating a formal report that highlights CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations to review before archiving the change.

Can I generate a structured verification report for change implementations?

Yes, you can generate a formal verification report by providing the change name and triggering the verification process. The report applies structured checks across requirements, scenarios, and design decisions, then outputs prioritized CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations for teams to review before archiving.

Does verification work without additional dependencies or components?

Yes, verification works as a standalone process with no listed dependencies or components required. You provide the change name to trigger verification, which applies structured checks across requirements, scenarios, and design decisions to assess completeness, correctness, and coherence, generating a formal report with prioritized issues and actionable recommendations.

Why does my change implementation fail correctness checks against design decisions?

Change implementations fail correctness checks when the code does not align with associated delta specifications, tasks, or design decisions. The verification process applies structured checks to assess completeness, correctness, and coherence, generating a report that highlights specific CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations to resolve discrepancies.