openspec-verify-change

Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-verify-change/SKILL.md

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and clearly sequenced, with executable commands, exact issue/recommendation templates, and exhaustive handling of edge cases. The main costs are token redundancy from repeated skip-semantics rules and the absence of any reference-file split for detailed verification rules.

Suggestions

State the not-applicable vs. not-verified semantics once (e.g., in step 4) and reference that definition from steps 5, 6, and 8 instead of restating the rules in each check.

Move the REMOVED/RENAMED delta-verification rules (step 5) and the report/output format (step 8) into a references/ file (e.g., delta-checks.md, report-format.md) and link them from SKILL.md.

Condense the store-selection and root-check preambles into a short decision list; phrases like "do not infer completion from the listed tasks alone" largely repeat earlier constraints and can be merged.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining known concepts and consists of project-specific operational rules, but the not-applicable/not-verified semantics are restated across steps 4, 5, 6, and 8, and the store/root preambles carry repeated defensive clauses ("do not infer", "never") that could be tightened.	3 / 5
Actionability	Copy-paste-ready commands (openspec status --change "<name>" --json), exact issue strings and recommendation templates, a concrete markdown report block, and a file:line reference format cover the common verification cases fully.	5 / 5
Workflow Clarity	A clear 8-step sequence with validation as its core, explicit checkpoints (parse JSON before acting, prompt when ambiguous, surface error message/fix for store-resolution failures), graded issue priorities, and a fully specified final-assessment branch for every issue/skip combination.	5 / 5
Progressive Disclosure	No bundle files exist, so a ~220-line monolith inlines detail blocks (REMOVED/RENAMED delta-verification rules, report/output format) that belong in reference files; internal structure is good, placing it above the minimal-structure anchor but below well-split content.	3 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when structure and literal command-phrase triggers. Its only weakness is specificity: it states a single verification action rather than enumerating the concrete operations involved.

Dimension	Reasoning	Score
Specificity	"Verify implementation matches OpenSpec change artifacts" names the domain and one concrete action with its three dimensions (complete, correct, coherent), but does not list several distinct operations as the 4/5 anchors require.	3 / 5
Completeness	Explicitly answers both what (verify implementation matches OpenSpec change artifacts) and when, with concrete trigger phrases including exact command utterances, matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	Natural phrases ("validate that implementation is complete... before archiving") plus literal user utterances ("openspec verify", "opsx verify") give good coverage; a few common synonyms like "check the change" are missing, short of the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche (OpenSpec change verification before archiving) with named CLI command triggers; minimal overlap risk with any other skill.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Fission-AI/OpenSpec
Path: skills/openspec-verify-change/SKILL.md
Commit: 2500d6d

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.