openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: edwardsnjd

Verify code implementations against openspec change artifacts and requirements.

9|1|Updated Jun 6, 2018

Search Tags:#testing #code review #implementation #verification #compliance #openspec

Ready to run

npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-verify-change-edwardsnjd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/edwardsnjd/dot-files/tree/main/configuration/agents/.agents/skills/openspec-verify-change
Command: npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-verify-change-edwardsnjd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately reflect design specifications, tasks, and overall project requirements, preventing discrepancies before archiving work.

Core Features & Use Cases

Completeness Check: Verifies that all defined tasks are addressed and requirements are covered.
Correctness Validation: Assesses if the implementation aligns with specified requirements and scenarios.
Coherence Review: Checks adherence to design decisions and coding patterns.
Use Case: Before merging a new feature, use this Skill to confirm that all user stories are implemented, the code follows established patterns, and the design documentation is respected.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the 'user-authentication' change.

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 design specifications and requirements?▼

You can verify code implementation against design specifications by using a validation tool that checks task completion, requirement mapping, and scenario coverage. This ensures your code accurately reflects the specified change artifacts before archiving.

What is the best way to check if code changes match project requirements before merging?▼

The best way to check if code changes match project requirements before merging is to perform a completeness and correctness validation. This process assesses whether all defined tasks are addressed and if the implementation aligns with specified scenarios.

How does spec coverage analysis work for code review?▼

Spec coverage analysis for code review works by assessing completeness, correctness, and coherence. It analyzes task completion, requirement mapping, scenario coverage, design adherence, and code pattern consistency against your change artifacts.

Do I need the openspec CLI to validate implementation compliance?▼

Yes, you need the openspec CLI to validate implementation compliance. The CLI is required to list changes, check status, and apply instructions for retrieving the design documents, tasks, and requirements artifacts needed for verification.

Can I check code pattern consistency and design adherence automatically?▼

Yes, you can check code pattern consistency and design adherence automatically through a coherence review. This validates that your implementation correctly follows established design decisions and coding patterns specified in your project artifacts.

Why does my implementation verification fail on spec coverage and requirement mapping?▼

Implementation verification fails on spec coverage and requirement mapping when defined tasks are not fully addressed or the code does not align with specified requirements. The validation process detects these discrepancies to prevent archiving incomplete work.