openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: PBH-BTN

Automate verification of implementations against OpenSpec change artifacts.

6.2k|152|Updated Feb 7, 2024

Search Tags:#testing #requirements #verification #OpenSpec #code-review #change-artifacts

Ready to run

npx skills add https://github.com/PBH-BTN/PeerBanHelper --skill openspec-verify-change-pbh-btn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/PBH-BTN/PeerBanHelper/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/PBH-BTN/PeerBanHelper --skill openspec-verify-change-pbh-btn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that an implementation matches the change artifacts produced by the OpenSpec workflow, ensuring completeness, correctness, and coherence before archiving.

Core Features & Use Cases

Artifact-based verification: Validates that specs, tasks, and design artifacts are implemented or properly mapped to code.
Delta-spec inspection: Reads delta specs from openspec/changes/<name>/specs/ to identify requirements and scenarios that require coverage.
Automated reporting: Generates a structured verification report detailing task completion, requirement coverage, and design alignment.

Quick Start

Provide the change name when prompted. The tool will load artifacts from the corresponding OpenSpec change folder, compare them against the codebase, and emit a 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 implementation correctness against OpenSpec change artifacts?▼

To verify implementation correctness against OpenSpec change artifacts, provide the change name to load specs, tasks, and design artifacts from the corresponding folder, generating a structured verification report detailing completeness and coherence.

What is OpenSpec delta spec inspection used for?▼

Delta spec inspection reads delta specs from openspec/changes/<name>/specs/ to identify requirements and scenarios that require code coverage, ensuring that implementation changes are properly mapped and validated before archiving.

Do I need the OpenSpec CLI to automate verification reporting?▼

Yes, the OpenSpec CLI is required to generate and read context for verification reporting. It builds the structured report detailing task completion, requirement coverage, and design alignment by parsing context files and artifacts.

How do I check if specs and tasks are implemented in my codebase?▼

To check if specs and tasks are implemented, the verification process compares artifacts from the OpenSpec change folder against the codebase, validating that design artifacts are properly mapped to code and emitting a coverage report.

When should I run artifact-based verification in the software engineering workflow?▼

Artifact-based verification should be run before archiving a change to ensure completeness, correctness, and coherence, confirming that the implementation matches the produced specs, tasks, and design artifacts.

What limitations exist when verifying OpenSpec changes against artifacts?▼

Verification is limited to changes that include specs, tasks, and design artifacts, and it requires the OpenSpec CLI to generate context files, meaning it cannot validate changes lacking these structured artifacts or CLI support.