skills.rest
ssd-mkdocs-platform
ssd-mkdocs-platformOFFICIAL
Explore all skills by this author →
GitHub

openspec-verify-change

Validate a selected change against specifications and artifacts using the openspec CLI.

1|Updated Feb 7, 2026
Search Tags:#testing#spec-driven#quality-assurance#openspec#code-review#artifact-validation#change-verification
One-click install
npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-verify-change-ssd-mkdocs-platform
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/ssd-mkdocs-platform/teams-board/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-verify-change-ssd-mkdocs-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow provides a structured way to validate that a change's implementation matches the associated specifications and artifacts, ensuring quality before archiving.

Core Features & Use Cases

  • Validate alignment between specifications, code changes, and artifacts to prevent misalignment.
  • Generate a formal verification report covering completeness, correctness, and coherence with actionable remediation guidance.
  • Integrate with change-management workflows to gate archiving on verified results.

Quick Start

Run the verification to ensure the current change aligns with its specs and artifacts before archiving.

Frequently Asked Questions about openspec-verify-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate code changes against specifications before archiving?▼

To validate code changes against specifications before archiving, retrieve the change status and associated artifacts to determine completeness, generating a structured verification report detailing correctness and coherence with actionable recommendations.

What is spec-driven change verification and when do I need it?▼

Spec-driven change verification is the process of validating that a change's implementation matches its associated specifications and artifacts. You need it to prevent misalignment and ensure quality before archiving changes.

How do I generate a formal verification report for completeness and correctness?▼

Generate a formal verification report by identifying an available change via the openspec CLI, retrieving its status and artifacts, and evaluating completeness and correctness to produce actionable remediation guidance.

Can I gate change archiving on verified validation results?▼

Yes, you can integrate with change-management workflows to gate archiving on verified results. The generated verification report details coherence and completeness to ensure quality before archiving.

What's the best way to check alignment between specifications and code artifacts?▼

The best way to check alignment between specifications and code artifacts is to validate the change using the openspec CLI, retrieving status and artifacts to determine coverage and generate a structured verification report.

Related Skills

Explore More Software Engineering Skills→
mrclrchtrmrclrchtr
54

openspec-ff-change

Generate OpenSpec change artifacts in dependency order using the openspec CLI.

Community
Advanced
MeetTechnologyMeetTechnology

openspec-verify-change

Verifies code changes against openspec delta specs and tasks.

Community
Advanced
YuDefineYuDefine
45

spectra-verify

Verify alignment between delta specs and code artifacts in change workflows.

Official
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

change-impact-analyzer

Analyze change impact and validate delta specifications for brownfield systems.

Community
Advanced