openspec-verify-change

Verify implementation matches OpenSpec change artifacts with prioritized findings.

Updated Feb 12, 2021
One-click install
npx skills add https://github.com/echowaves/WiSaw.cdk --skill openspec-verify-change-echowaves
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/echowaves/WiSaw.cdk/tree/main/.roo/skills/openspec-verify-change
Command: npx skills add https://github.com/echowaves/WiSaw.cdk --skill openspec-verify-change-echowaves

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you confirm that code and work products fully match the change’s specs, tasks, and design artifacts so you can archive with confidence instead of guessing.

Core Features & Use Cases

  • Completeness checks: Verifies task checkboxes are marked complete and that all requirements from delta specs are present in the codebase.
  • Correctness checks: Assesses whether implementation evidence aligns with requirement intent and whether scenarios appear covered (including test presence).
  • Coherence checks: Compares implementation against design decisions when design artifacts are available.
  • Verification reporting: Produces a structured report with a scorecard and prioritized CRITICAL/WARNING/SUGGESTION issues.

Quick Start

Run openspec-verify-change by selecting a change (or providing a change name) so the skill generates a completeness, correctness, and coherence verification 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 my implementation matches change specs before archiving?

You verify implementation against change artifacts by checking task completion, delta spec requirements, scenario coverage, and optional design adherence, producing a prioritized report with confidence-graded findings to archive with confidence.

What does spec-driven development verification check for task completion?

Spec-driven development verification checks completeness by confirming task checkboxes are marked complete and validating that all requirements from delta specs are present in the codebase before archiving a change.

How do I check scenario coverage and test presence for a code change?

Scenario coverage assessment evaluates whether implementation evidence aligns with requirement intent and confirms that scenarios appear covered, including verifying test presence for the selected change.

Can I compare implementation against design decisions during change verification?

Yes, coherence checks compare implementation against design decisions when design artifacts are available, ensuring the codebase aligns with established design decisions before archiving the change.

How do I generate a verification report for spec-driven development changes?

You generate a verification report by selecting a change or providing a change name, which loads artifacts via openspec instructions and outputs a structured scorecard with prioritized CRITICAL, WARNING, and SUGGESTION findings.

Do I need design artifacts to run completeness and correctness checks on a change?

Design artifacts are optional for completeness and correctness checks, which verify task completion and requirement alignment, but are needed for coherence checks that compare implementation against design decisions.