skills.rest
sitdownkevin
sitdownkevinCOMMUNITY
Explore all skills by this author →
Website𝕏@sitdownkevinGitHub

openspec-verify-change

Verify implemented code against openspec delta change artifacts.

1|Updated May 7, 2024
Search Tags:#automation#testing#qa#verify#openspec#spec-validation#change-artifacts
One-click install
npx skills add https://github.com/sitdownkevin/blog-next --skill openspec-verify-change-sitdownkevin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/sitdownkevin/blog-next/tree/main/.cursor/skills/openspec-verify-change
Command: npx skills add https://github.com/sitdownkevin/blog-next --skill openspec-verify-change-sitdownkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that an implementation aligns with change artifacts (specs, tasks, design) to ensure completeness and coherence before archiving.

Core Features & Use Cases

  • End-to-end verification of change implementations against delta specs, including tasks, requirements, and scenarios.
  • Generates a structured verification report detailing completeness, correctness, and coherence.
  • Guides teams through remediation with actionable recommendations and file/line references.

Quick Start

Provide a change name to verify and let the tool generate 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 my implementation matches change artifacts before archiving?▼

To verify implementation matches change artifacts, provide a change name to generate a structured report detailing discrepancies in completeness, correctness, and coherence against delta specs, tasks, and design.

What is spec-validation for change artifacts in software engineering?▼

Spec-validation for change artifacts is the process of identifying and reporting discrepancies between delta specs and implemented code to ensure accuracy, completeness, and coherence across the project before archival.

How do I check if implemented code aligns with openspec delta specs and tasks?▼

Checking if implemented code aligns with openspec delta specs requires loading context from change artifacts to assess correctness and coherence, producing a structured verification report with actionable file and line references.

Do I need the openspec CLI to validate code against change artifacts?▼

Yes, you need the openspec CLI and access to change artifacts to load context and produce a structured verification report assessing implementation completeness and correctness.

What does a verification report for change artifacts include?▼

A verification report for change artifacts includes details on implementation completeness, correctness, and coherence, guiding teams through remediation with actionable recommendations and specific file and line references.

Why does my implementation verification fail before archiving openspec changes?▼

Implementation verification fails before archiving openspec changes when discrepancies exist between the change artifacts and the implemented code, which the structured report identifies across completeness, correctness, and coherence dimensions.

Related Skills

Explore More Software Engineering Skills→
rangechowrangechow

openspec-verify-change

Verify change implementations against openspec artifacts for completeness, correctness, and coherence.

Community
Advanced
lz-freedomlz-freedom

openspec-verify-change

Verify change artifacts for completeness, correctness, and coherence before archiving.

Community
Advanced
memorysavermemorysaver

openspec-verify-change

Verify implementation completeness against openspec delta spec artifacts.

Community
Advanced
Draft-OfficialDraft-Official

openspec-verify-change

Verify implementation matches change specifications and test scenarios across codebases.

Official
Advanced