openspec-verify-change

Verify code implementations against specifications, tasks, and design documents.

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-verify-change-blackbelttechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-verify-change-blackbelttechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code implementations accurately reflect the defined change artifacts, such as specifications, tasks, and design documents, before a change is finalized or archived.

Core Features & Use Cases

  • Completeness Check: Verifies that all defined tasks are completed and all specified requirements are addressed in the code.
  • Correctness Validation: Assesses if the implementation aligns with requirement intent and if scenarios are adequately covered by code or tests.
  • Coherence Assessment: Checks adherence to design decisions and consistency with established code patterns.
  • Use Case: After developing a new feature based on a set of requirements and design documents, use this Skill to generate a report confirming that all aspects of the change have been correctly implemented and are coherent with the project's standards.

Quick Start

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

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 change specifications and design documents?

To verify code implementation against change specifications, this Skill invokes the openspec CLI to retrieve change details and analyzes code against specifications, tasks, and design documents.

What is compliance verification for code changes and when do I need it?

Compliance verification for code changes ensures implementations accurately reflect defined change artifacts before finalization. You need it after developing a new feature to confirm all tasks, requirements, and design decisions are correctly addressed and coherent with project standards.

How do I check if all defined tasks and requirements are completed in my code?

To check if all defined tasks and requirements are completed in your code, perform a completeness check using this Skill to verify that all specified requirements are addressed and all defined tasks are finished in the implementation.

Does openspec-verify-change work with the openspec CLI to validate implementation correctness?

Yes, openspec-verify-change works with the openspec CLI to validate implementation correctness. It operates by invoking the CLI to retrieve change details and mapping implementations to requirements and scenarios to assess correctness.

How do I assess code pattern consistency and design adherence during a code review?

To assess code pattern consistency and design adherence during a code review, use this Skill's coherence assessment feature to evaluate how well the implementation aligns with established design decisions and project code patterns.

What are the limitations of using change artifacts for implementation verification?

The limitation of using change artifacts for implementation verification is that it operates strictly within the openspec ecosystem, meaning it cannot verify implementations that lack associated specifications, tasks, or design documents retrieved via the openspec CLI.