skills.rest
tungnguyen10
tungnguyen10COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-verify-change

Validate implementation work against openspec change artifacts before archiving.

Updated Jan 18, 2026
Search Tags:#implementation#verification#change management#spec compliance#openspec#requirement validation#pre-archive check
One-click install
npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-verify-change-tungnguyen10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/tungnguyen10/iuh_department/tree/main/.agents/skills/openspec-verify-change
Command: npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-verify-change-tungnguyen10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When implementing changes based on openspec artifacts (specs, tasks, design documents), it is easy to miss incomplete tasks, unimplemented requirements, or deviations from the agreed design, leading to low-quality code that requires rework before archiving. This Skill eliminates that risk by automating pre-archive validation of your implementation.

Core Features & Use Cases

  • Task Completion Check: Automatically parses task checklists to flag any incomplete tasks that need to be finished before archiving.
  • Requirement Coverage Validation: Cross-references delta specs with your codebase to confirm all defined requirements have corresponding implementation.
  • Design Adherence Review: Checks that your code follows the key decisions and patterns outlined in the change's design document, and flags inconsistencies with project coding standards.
  • Use Case: A developer who just finished implementing a new feature from an openspec change can use this Skill to quickly confirm all work is complete and aligned with the original artifacts before marking the change as archived.

Quick Start

Use the openspec-verify-change skill to validate that your implementation for the selected openspec change is fully complete, correct, and coherent before you archive the work.

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 implementation matches specs before archiving changes?▼

Spec compliance verification checks that software implementation matches associated openspec change artifacts including specifications, task lists, and design documents. It cross-references delta specs with your codebase to confirm all defined requirements have corresponding implementation before archiving.

What does pre-archive validation for spec-driven development check?▼

Pre-archive validation checks task completion by parsing checklists to flag incomplete tasks, validates requirement coverage by cross-referencing delta specs with code, and reviews design adherence to confirm code follows key decisions and patterns from the change's design document.

How do I automate requirement coverage validation for openspec changes?▼

Automate requirement coverage validation by cross-referencing delta specs with your codebase to confirm all defined requirements have corresponding implementation. This prevents incomplete or divergent code changes from being archived in spec-driven workflows.

Can I use openspec-verify-change to flag incomplete tasks before archiving?▼

Yes, openspec-verify-change automatically parses task checklists to flag any incomplete tasks that need to be finished before archiving. This eliminates the risk of missing incomplete tasks during pre-archive validation.

How do I check if my code follows the design document in spec-driven development?▼

Design adherence review checks that your code follows the key decisions and patterns outlined in the change's design document. It flags inconsistencies with project coding standards to prevent deviations from the agreed design before archiving.

When do I need pre-archive validation for implementation completeness?▼

Pre-archive validation is needed when implementing changes based on openspec artifacts like specs, tasks, and design documents. It prevents incomplete tasks, unimplemented requirements, or design deviations from leading to low-quality code that requires rework.

Related Skills

Explore More Software Engineering Skills→
Pony-UnicornPony-Unicorn
7

openspec-continue-change

Generate the next required OpenSpec artifact according to a workflow schema.

Community
Advanced
mufengbufengmufengbufeng
1

openspec-archive-change

Archive completed changes to date-prefixed paths with openspec CLI.

Community
Advanced
MeetTechnologyMeetTechnology

openspec-apply-change

Guide OpenSpec change selection, status checks, and task execution.

Community
Advanced
sunholo-datasunholo-data
33

Design Spec Auditor

Verify code implementations against design specifications and generate compliance reports.

Community
Basic