skills.rest
lbrlabs
lbrlabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-verify-change

Validate change implementation against specs, tasks, and design artifacts.

9|4|Updated Jun 13, 2023
Search Tags:#validation#qa#verify#openspec#code-review#change-artifacts#spec-delta
One-click install
npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-verify-change-lbrlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/lbrlabs/pulumi-lbrlabs-eks/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-verify-change-lbrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a change implementation aligns with its artifacts (specs, tasks, and design) so teams can confidently archive completed work.

Core Features & Use Cases

  • Validates delta specs and associated tasks exist and are traceable to code.
  • Checks status, collects artifacts, and produces a structured verification report.
  • Provides actionable remediation guidance to resolve gaps before archiving.

Quick Start

Run the verification flow for a change using openspec to generate the 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 code changes against design specs before archiving?▼

A spec delta refers to the specific modifications added to existing specifications during a change. Validating spec deltas ensures new code implementation correctly aligns with updated design artifacts and task requirements before archiving.

What does a verification report for change artifacts include?▼

A verification report for change artifacts includes checks for completeness, correctness, and coherence by validating task completion, spec coverage, and design adherence, while providing actionable remediation guidance to resolve any identified gaps.

How do I validate that task checklists are traceable to code implementation?▼

Validating task checklist traceability to code implementation requires loading change artifacts via the openspec workflow to confirm that every task status is complete and directly maps to the corresponding delta spec and design context.

What is the best way to check spec coverage and design adherence for a new change?▼

The best way to check spec coverage and design adherence is to run an automated verification flow that collects change artifacts and evaluates them against the implementation to produce a structured review report prior to archiving.

Why does my change implementation fail coherence checks before archiving?▼

Change implementation fails coherence checks before archiving when gaps exist between the code and the change artifacts, meaning task checklists are incomplete, spec coverage is missing, or the implementation deviates from the recorded design.

Related Skills

Explore More Software Engineering Skills→
goerngoern
113

openspec-verify-change

Verify implementation matches delta specs, tasks, and design artifacts.

Community
Advanced
aroca89aroca89

sdd-archive

Merge delta specs and verification artifacts into the main spec repository.

Community
Advanced
sgiathsgiath
4

openspec-verify-change

Verify code changes against openspec tasks, specs, and design artifacts.

Community
Advanced
dain-agencydain-agency

migrate-verify

Cross-reference migration manifests with codebase files to verify task completion.

Official
Advanced