OpenSpec Change Verification FAQs

Question 1

What is the primary purpose of openspec-verify-change?

Accepted Answer

It is designed to verify that a code implementation matches its corresponding change artifacts, such as specifications, tasks, and design documents, before the work is archived.

Question 2

How does the skill handle incomplete tasks?

Accepted Answer

It parses tasks.md for incomplete checkboxes, flags them as CRITICAL issues in the verification report, and provides specific recommendations to either complete the code or update the task list.

Question 3

Do I need external tools to use this skill?

Accepted Answer

Yes, this skill requires the OpenSpec CLI to be installed and accessible in your environment to fetch and analyze project change artifacts.

Question 4

What happens if I don't have all the OpenSpec artifacts?

Accepted Answer

The skill features graceful degradation. If specific files like design.md or specs are missing, it will skip those specific checks and clearly note which dimensions were not verified.

Question 5

How are the verification results presented?

Accepted Answer

Results are provided as a Markdown report featuring a summary scorecard and a prioritized list of issues categorized as CRITICAL, WARNING, or SUGGESTION, complete with file and line references.

OpenSpec Change Verification

Key Features

Use Cases

OpenSpec Change Verification

Key Features

Use Cases